Larry Wall Quotes
born 1954 United States
Larry Arnold Wall (born September 27, 1954) is a programmer, best known as the creator of the Perl programming language.
- United States
- Engineers
- Programmers
Also known as: Larry wall, Wall, Larry
Random Larry Wall quote
257 quotes
And we can always supply them with a program that makes identical files into links to a single file.
People who understand context would be steamed to have someone else dictating how they can call it.
But you have to allow a little for the desire to evangelize when you think you have good news.
I want to see people using Perl to glue things together creatively, not just technically but also socially.
Maybe we should take a clue from FTP and put in an option like 'print hash marks on every 1024 iterations'.
Perl itself is usually pretty good about telling you what you shouldn't do.
Besides, it's good to force C programmers to use the toolbox occasionally.
There's some entertainment value in watching people juggle nitroglycerin.
There ain't nothin' in this world that's worth being a snot over.
Of course, this being Perl, we could always take both approaches.
The way I see it, if you declare something portable, you'll always be wrong, and if you declare it non-portable, you'll always be right.
That could certainly be done, but I don't want to fall into the Forth trap, where every running Forth implementation is really a different language.
The court finds everyone to be in contempt (including himself :-), and orders everyone sentenced to five years hard labor. (Working on Perl, of course.)
Almost nothing in Perl serves a single purpose.
They can always run stderr through uniq.
Think of prototypes as a funny markup language--the interpretation is left up to the rendering engine.
And other operators aren't so special syntactically, but weird in other ways, like 'scalar', and 'goto'.
Would you trust the linguistic intuitions of someone who has been studying Latin or Greek for three days?
Magically turning people's old scalar contexts into list contexts is a recipe for several kinds of disaster.
Not that I'm against sneaking some notions into people's heads upon occasion. (Or blasting them in outright.)