> > the dogmatic, narrow view of regular C programmers.
>
> There are benefits to C++ even for the casual programmer or for the new student to
> the language. But I cannot see any benefits for the professional or the serious
> student.
>
> I studied C in college and found it difficult at first, then as I progressed, the
> language taught me how to be more methodical, focused and structured in my
> programming tasks.
>
> Roll on five years later when I went back to college and studied C++ and was baffled
> yet again on it's use. Luckily I was able resort to standard C to finish the course,
> due to the constraints imposed by C++ at the time (i.e. poor exception handling).
> Even my lecturers advised resorting to C to resolve the problems experienced with
> C++.
>
> Now exploring the OOP part of college with C#, it amazes me why coders are so lazy
> today, true we are all standing on the shoulders of giants but lazy giants at that.
>
> Granted I am not a Jedi C coder by any wide margin, but it is clear where the bloat
> comes from. If not the coder but from the language. We can argue Moore's two laws,
> but it irks me to think that it should be an excuse for bloat.
>
> I think C therefore I code C should be maintained, and all these other derivatives of
> C should be ignored.
>
> If MAME reverted back to C, I'm sure there would be less bloat and more efficiency
> without having resort to Moore's poor excuse, as I have seen it so many times, posted
> here.
>
> IMHO.
I think you're just sorry because you couldn't set everything as global variables to solve your problems. :P At least that's what most C# programmers use to call a constraint. The good code is not made by the language you use (though it helps) but the programmer.
Now you will tell us everyone should still use assembler to speed up emulation after year 2000. Good luck maintaining code through SVN like that.
|
Index 
Flat 
Re: C versus C++ with regard to MAME
Reply
