Before everyone rushes out to defend golfing (too late), consider this...
When I golf, and I am guessing this is pretty typical, I basically slap some line noise together, and see what happens when it runs. I might edit and execute my program hundreds of times, but this is no biggee...I have a syntax highligting editor that catches typos, a shell with command line history, a windowing OS, browser open to hyperlinked man pages, and my own box with cycles to burn. If I get too clever and screw something up, I spend 99% of my time debugging, and almost none wrestling with the environment.
Now consider the programming environment of 1972. Punch cards, line editors, batched jobs on shared mainframes, byzantine manuals on dead trees...editting, compiling, executing code, and reading docs was a pain in the ass. It could literally take hours to learn your program had a fatal one character typo.
Given all this, I think I would stay aware from "clever" progamming languages, too. At least for a little while...:)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||