Re: When my script doesn't work, I ...

[Ratazong]

in reply to When my script doesn't work, I ...

Well - a non-working script is normal for me. In Perl I'm used to write just a couple of lines, run them, debug them and then continue. (*) Actually I'm much more concerned if a script runs faultless on the first try. Then I have the really bad feeling that I have overlooked something and something went terribly wrong.

Rata

(*) a couple of years ago I was developing in a huge telecommunication-environment using CHILL. There we had linkage-times of 2-3 weeks! You really had to plan what (and how) to do before submitting your code. And of course you didn't want to be the reason if a linkage failed ... the "try out what happens"-approach I use in Perl is so much nicer! :-)

[jmlynesjr]

Back in the 70s, I supported a utility power control system of about 100,000 lines of assembler code(Lockheed Electronics LEC-16). The code couldn't be assembled and linked on-site, so we got one shot per year on a cross-complier and linker at the vender's home office. The rest of the year, all changes were made via hand assembled patches, some 1000s of lines long. The good old days...

James