This company did some records-tracking software in a truly mission-critical industry. I applied for the job, went down and talked to their head programmer guy. He did all the software himself. It's clear it was one of those "just get the guy to write it and get it working" situations. He wrote Perl as COBOL or BASIC. No use of any Perl string-handling, for example, much less objects or any other sort of post-1980s features.
And, it was all code like this:
$a = substr( $foo, 4, 3 ); print $a, " widgets found\n"; close BAR;
if ( $x == 3 ) { print "Do you want to bar?" } else { print
"Do you want to wango?" } open( FOO, "<$filename" ); $q = <FOO>;
#... etc etc etc
He explained that he likes to put as much code on one line as he can so that he can see as much code as he can on the screen at one time. In Notepad, mind you.
I told him that if I came on board I could help them immensely, and that
I would have to redo their entire way of doing things. He wanted a
code-monkey to crank out some patches. He realized that we were not a
fit.
Now, this was two years ago, so I don't know what they're like now. It was easily the worst Perl I'd ever seen.
Bad Perl (Score:2)
Re:Bad Perl (Score:2)
--
xoa
MJD's program repair shop (Score:1)
MJD's program repair shop [plover.com] is an oasis of such code.
dc