Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I like it when programs march on stubbornly in the face of impossible odds. It makes me feel smarter than them.

    There is historical justification for a compiler to do this. Back in the days of punch cards and line printers, the time between submitting a job to compile a program and seeing the result was measured in minutes, hours, or days. So, it was extremely important for the compiler to tell you about as many errors as possible in a single run so that you could fix as much as possible before sending the job back again.

    Nowadays, with interactive computers, the sumit/run/result cycle is measured in fractions of a second - so you just fix the first error and don't even try to figure out which of the following errors are cascaded consequences of the first and which are separate errors but just compile it again immediately.