David Megginson <[EMAIL PROTECTED]> said: > Tony Peden writes: > > > I don't know, maybe it's just me but I've written a lot of perl I > > couldn't read a month later ... > > You just haven't rewired your brain chemistry yet. After about 12 > years, perl code starts to look normal and everything else (C/C++, the > sky, your family) looks strange. >
Hehe... Well, you know, not being able to read the code a month later could be a good thing. You see, if you are working with one of those slick self documenting Basic derivative or natural/english language derivative or what-ever-is-like-a-cpu-with-esp derivative languages you are able to go back in to the code a year later and easily understand what is going on, apply a quick modification, run a few tests, and deploy all before lunch. Only to find out a week later that a huge bug has been introduced that has left the database hopelessly corrupted and erroneously distributed tens of thousands of dollars in cash to customers. The company goes into Chapter 11 and of course you, the programmer, are now unemployed with a big black splotch on your resume. Since you are now home all the time, your family and the sky, etc., all start to look _really_ familiar. Perl must be better then, since it makes you think about what you are doing, before you do it. :-) Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
