One of the good things about learning to code in x86 / z80 asm, then 'C' in the 80's was that optomizing your code just became something you did. It was a necessity because of the slow processor/memory of the time. Think 'direct screen writing' on the old DOS pc's. It's one of the reasons I preach kids to learn 'C' before they learn C++ or Java or C# or VB.NET. These languages breed sloppy, lazy coding (sorry if I offend anyone, but I've got enough years experience now to know that that is a true statement). Part of that is the OOP paradigm we all try to strive for today. It IS a good thing. I agree. The design of systems using OOP techniques is better, easier. But coding should still be second nature to young, up and coming geeks before we teach them design patterns...
sorry, having a sloppy code day myself.... POINTERS RULE!!!! Michael Tyler Littlefield wrote: > > > well put, chris. > I think a few people on this list have a pointerfobia. And then again, > there's always the "It's modern technology. What should it matter if > it takes 5 cycles or 500, they are faster than they used to be. > I'd hate to see coding 10 years down the road. > > Thanks, > Tyler Littlefield > Web: tysdomain.com > email: [email protected] <mailto:tyler%40tysdomain.com> > My programs don't have bugs, they're called randomly added features. > > - >
