The Full Wiki

Larry Wall: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

Larry Wall
Born September 27, 1954 (1954-09-27) (age 55)
Nationality US American
Occupation Programmer, Author
Known for Perl
Religious beliefs International Church of the Nazarene
Spouse(s) Gloria Wall
Children 4

Larry Wall (born September 27, 1954) is a programmer and author, most widely known for his creation of the Perl programming language in 1987.



Wall earned his bachelor's degree from Seattle Pacific University in 1976.

While in graduate school at UC Berkeley, Wall and his wife were studying linguistics with the intention afterwards of finding an unwritten language, perhaps in Africa, and creating a writing system for it. They would then use this new writing system to translate various texts into the language, among them the Bible. Due to health reasons these plans were canceled, and they remained in the U.S., where Larry instead joined the NASA Jet Propulsion Laboratory after he finished graduate school.[1]


Wall is the author of the rn Usenet client and the nearly universally used patch program. He has won the International Obfuscated C Code Contest twice and was the recipient of the first Free Software Foundation Award for the Advancement of Free Software in 1998.

Beyond his technical skills, Wall is known for his wit and often sarcastic sense of humour [2] , which he displays in the comments to his source code or on Usenet. For example: "We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise," and:

For example, it's been several decades now since a certain set of Bible translations came out, and you'll notice a pattern: the New English Bible, the New American Standard Bible, and the New International Version, to name a few. It's really funny. I suspect we'll still be calling them “new this” and “new that” a hundred years from now. Much like New College at Oxford. Do you know when New College was founded. Any guesses? New College was new in 1379. [2]

He is the co-author of Programming Perl (often referred to as the Camel Book), which is the definitive resource for Perl programmers. He has edited the Perl Cookbook. His books are published by O'Reilly.

Wall's qualification as a linguist is apparent in his books, interviews, and lectures. He often compares Perl to a natural language and explains his decisions in Perl's design with linguistic rationale. He also often uses linguistic terms for Perl language constructs, so instead of traditional "variable", "function", and "accessor" he sometimes says "noun", "verb", and "topicalizer".

Wall's Christian faith has influenced some of the terminology of Perl, such as the name itself, a biblical reference to the "Pearl of great price" (Matthew 13:46). [1] Similar references are the function name bless, and the organization of Perl 6 design documents with categories such as apocalypse and exegesis. Wall has also alluded to his faith when he has spoken at conferences, including a rather straightforward statement of his beliefs at the August, 1997 Perl Conference and a discussion of Pilgrim's Progress at the YAPC (Yet Another Perl Conference) in June, 2000.

Wall continues to oversee further development of Perl and serves as the Benevolent Dictator for Life of the Perl project. His role in Perl is best conveyed by the so-called 2 Rules, taken from the official Perl documentation:

  1. Larry is always by definition right about how Perl should behave. This means he has final veto power on the core functionality.
  2. Larry is allowed to change his mind about any matter at a later date, regardless of whether he previously invoked Rule 1.
Got that? Larry is always right, even when he was wrong.[3]

Virtues of a programmer

Wall along with Randal L. Schwartz and Tom Christiansen writing in the second edition of Programming Perl, outlined the Three Virtues of a Programmer:

  1. Laziness - The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer. Also hence, this book. See also impatience and hubris.
  2. Impatience - The anger you feel when the computer is being lazy. This makes you write programs that don't just react to your needs, but actually anticipate them. Or at least pretend to. Hence, the second great virtue of a programmer. See also laziness and hubris.
  3. Hubris - Excessive pride, the sort of thing Zeus zaps you for. Also the quality that makes you write (and maintain) programs that other people won't want to say bad things about. Hence, the third great virtue of a programmer. See also laziness and impatience.

See also


  1. ^ Sims, David (1998-04-98). Q&A With Larry Wall, Creator Of Perl, David Sims "Q&A With Larry Wall, Creator Of Perl". TechWeb. Q&A With Larry Wall, Creator Of Perl, David Sims. Retrieved 2007-08-05.  
  2. ^ a b Wall, Larry; this is a recursive reference by a noted expert on Larry Wall (1999-03-03), "Perl, the first postmodern computer language", The following is the text of Larry Wall's talk at Linux World on Wednesday, March 3. He explains why Perl is a fitting language for the postmodern era. As a member of the audience commented: "Another mindbender from Larry.", San Jose Convention Centerr, San Jose, California: O’Reilly Media, Inc.,, retrieved 2007-11-19  
  3. ^ Perl 5.10.0 Documentation - perlhack,  

External links

This audio file was created from a revision dated 2006-06-27, and does not reflect subsequent edits to the article. (Audio help)
More spoken articles

Please note that as the State of the Onion speeches are often primarily based on visual humour, the transcripts may seem confusing or nonsensical.



Up to date as of January 14, 2010

From Wikiquote

Larry Wall is a programmer, best known as the creator of the Perl programming language.



Usenet postings


  • Although the Perl Slogan is There's More Than One Way to Do It, I hesitate to make 10 ways to do something.  :-)
  • And don't tell me there isn't one bit of difference between null and space, because that's exactly how much difference there is.  :-)
  • Because . doesn't match \n. [\0-\377] is the most efficient way to match everything currently. Maybe \e should match everything. And \E would of course match nothing.  :-)
  • Chip Salzenberg sent me a complete patch to add System V IPC (msg, sem and shm calls), so I added them. If that bothers you, you can always undefine them in  :-)
  • Piet van Oostrum: I find this a nice feature but it is not according to the documentation. Or is it a BUG?
    Larry Wall: Let's call it an accidental feature. :-)
  • If you want to program in C, program in C. It's a nice language. I use it occasionally...  :-)
  • It is, of course, written in Perl. Translation to C is left as an exercise for the reader.  :-)
  • It won't be covered in the book. The source code has to be useful for something, after all...  :-)
  • Dan Smith: I've tried (in vi) 'g/[a-z]\n[a-z]/s//_/'...but that doesn't cut it. Any ideas? (I take it that it may be a two-pass sort of solution).
    Larry Wall: In the first pass, install perl. :-)
  • There are probably better ways to do that, but it would make the parser more complex. I do, occasionally, struggle feebly against complexity...  :-)
  • There are still some other things to do, so don't think if I didn't fix your favorite bug that your bug report is in the bit bucket. (It may be, but don't think it.  :-)


  • Besides, including <std_ice_cubes.h> is a fatal error on machines that don't have it yet. Bad language design, there...  :-)


  •  : And it goes against the grain of building small tools.
    Innocent, Your Honor. Perl users build small tools all day long.
  • If I don't document something, it's usually either for a good reason, or a bad reason. In this case it's a good reason.  :-)
  • If you want to see useful Perl examples, we can certainly arrange to have comp.lang.misc flooded with them, but I don't think that would help the advance of civilization.  :-)
  • > (It's sorta like sed, but not. It's sorta like awk, but not. etc.)
    Guilty as charged. Perl is happily ugly, and happily derivative.
  • Lispers are among the best grads of the Sweep-It-Under-Someone-Else's-Carpet School of Simulated Simplicity. [Was that sufficiently incendiary?  :-)]
  • ...this does not mean that some of us should not want, in a rather dispassionate sort of way, to put a bullet through csh's head.
  • Unix is like a toll road on which you have to stop every 50 feet to pay another nickel. But hey! You only feel 5 cents poorer each time.


  • Well, enough clowning around. Perl is, in intent, a cleaned up and summarized version of that wonderful semi-natural language known as
  • Anyway, there's plenty of room for doubt. It might seem easy enough, but computer language design is just like a stroll in the park.

    Jurassic Park, that is.


  • I want to see people using Perl to glue things together creatively, not just technically but also socially.
  • As usual, I'm overstating the case to knock a few neurons loose, but the truth is usually somewhere in the muddle, uh, middle.
  • Of course, I reserve the right to make wholly stupid changes to Perl if I think they improve the language.  :-)
  • 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.
  • Tcl long ago fell into the Forth trap, and is now trying desperately to extricate itself (with some help from Sun's marketing department).
  • The whole intent of Perl 5's module system was to encourage the growth of Perl culture rather than the Perl core.
  • Life gets boring, someone invents another necessity, and once again we turn the crank on the screwjack of progress hoping that nobody gets screwed.
  • No prisoner's dilemma here. Over the long term, symbiosis is more useful than parasitism. More fun, too. Ask any mitochondria.
  • P.S. Perl's master plan (or what passes for one) is to take over the world like English did. Er, *as* English did...
  • I think you didn't get a reply because you used the terms 'correct' and 'proper', neither of which has much meaning in Perl culture.  :-)
  • We didn't put in ^^ because then we'd have to keep telling people what it means, and then we'd have to keep telling them why it doesn't short circuit.  :-/
  • Real theology is always rather shocking to people who already think they know what they think. I'm still shocked myself.  :-)
  • The following two statements are usually both true:
    There's not enough documentation.
    There's too much documentation.
  • The random quantum fluctuations of my brain are historical accidents that happen to have decided that the concepts of dynamic scoping and lexical scoping are orthogonal and should remain that way.
  • I'm serious about thinking through all the possibilities before we settle on anything. All things have the advantages of their disadvantages, and vice versa.
  • Part of language design is perturbing the proposed feature in various directions to see how it might generalize in the future.
  • It's appositival, if it's there. And it doesn't have to be there. And it's really obvious that it's there when it's there.
  • A 'goto' in Perl falls into the category of hard things that should be possible, not easy things that should be easy.
  • Well, that's more-or-less what I was saying, though obviously addition is a little more cosmic than the bitwise operators.
  • You tell it that it's indicative by appending $!. That's why we made $! such a short variable name, after all.  :-)
  • As someone pointed out, you could have an attribute that says 'optimize the heck out of this routine', and your definition of heck would be a parameter to the optimizer.
  • It is my job in life to travel all roads, so that some may take the road less travelled, and others the road more travelled, and all have a pleasant day.
  • It's getting harder and harder to think out loud. One of these days someone's gonna go off and kill Thomas a'Becket for me...
  • I was about to say, 'Avoid fame like the plague,' but you know, they can cure the plague with penicillin these days.
  • But the possibility of abuse may be a good reason for leaving capabilities out of other computer languages, it's not a good reason for leaving capabilities out of Perl.
  • P.S. I suppose I really should be nicer to people today, considering I'll be singing in Billy Graham's choir tonight...  :-)
  • Magically turning people's old scalar contexts into list contexts is a recipe for several kinds of disaster.
  • I wasn't recommending that we make the links for them, only provide them with the tools to do so if they want to take the gamble (or the gambol).
  • This has been planned for some time. I guess we'll just have to find someone with an exceptionally round tuit.
  •     switch (ref $@) {
        OverflowError =>
    warn 'Dam needs to be drained';
        DomainError =>
    warn 'King needs to be trained';
        NuclearWarError =>
  • If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee.
  • Historically Tcl has always stored all intermediate results as strings. (With 8.0 they're rethinking that. Of course, Perl rethought that from the start.)
  • To ordinary folks, conversion is not always automatic. It's something that may or may not require explicit assistance. See Billy Graham.  :-)
  • Well, you can implement a Perl peek() with unpack('P',...). Once you have that, there's only security through obscurity.  :-)
  • It may be possible to get this condition from within Perl if a signal handler runs at just the wrong moment. Another point for Chip...  :-)
  • The Harvard Law states: Under controlled conditions of light, temperature, humidity, and nutrition, the organism will do as it damn well pleases.
  • That gets us out of deciding how to spell Reg[eE]xp?|RE . . . Of course, then we have to decide what ref $re returns...  :-)
  • I was trying not to mention backtracking. Which, of course, means that yours is 'righter' than mine, in a theoretical sense.
  • Not that I'm against sneaking some notions into people's heads upon occasion. (Or blasting them in outright.)
  • (To the extent that anyone but a Prolog programmer can understand \X totally. (And to the extent that a Prolog programmer can understand 'cut'. :-))
  • Well, hey, let's just make everything into a closure, and then we'll have our general garbage collector, installed by 'use less memory'.
  • The way these things go, there are probably 6 or 8 kludgey ways to do it, and a better way that involves rethinking something that hasn't been rethunk yet.
  • I'm afraid my gut level reaction is basically, proceed is cute, but cute doesn't cut it in the emergency room.
  • Boss: You forgot to assign the result of your map!
    Hacker: Dang, I'm always forgetting my assignations...
    Boss: And what's that 'goto' doing there?!?
    Hacker: Er, I guess my finger slipped when I was typing 'getservbyport'...
    Boss: Ah well, accidents will happen. Maybe we should have picked APL.
  • And other operators aren't so special syntactically, but weird in other ways, like 'scalar', and 'goto'.


  • Er, Tom, I hate to be the one to point this out, but your fix list is starting to resemble a feature list. You must be human or something.
  • Well, you know, Hubbard had a bunch of people sworn to commit suicide when he died. So of course he never officially died...
  • I would estimate that the number of programs it breaks in the world will be less than 10. As long as one of those 10 isn't, we're probably okay.
  • I'm reminded of the day my daughter came in, looked over my shoulder at some Perl 4 code, and said, 'What is that, swearing?
  • Y'know, there are other possibilities if we assume that filenames are UTF-8...yikes...wait, put down that meat cleaver! Aieeee!!!
  •  : I could understand principles of Perl source in 2-3 days [. . .]

    Gee, it took me about eleven years.  :-)
  • There's often more than one correct thing.
    There's often more than one right thing.
    There's often more than one obvious thing.
  • 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.  :-)
  •  : Why Bible quotes exclusively? What happened to the Eastern religions?<BR>
    I'm still working on the Unicode mods.
  • Maybe we should take a clue from FTP and put in an option like 'print hash marks on every 1024 iterations'.  :-)
  • And besides, if Perl really takes off in the Windows space, I think the rest of us would just as soon have a double-agent within ActiveState.  :-)
  • The court finds everyone to be in contempt (including himself :-), and orders everyone sentenced to five years hard labor. (Working on Perl, of course.)
  • I view the JVM as just another architecture that Perl ought to be ported to. (That, and the Underwood typewriter...)
  • So please don't think I have a 'down' on the MVS people. I'm just pulling off their arms to beat other people over the head with.
  • It's, uh, pseudo code. Yeah, that's the ticket...
    And 'unicode' is pseudo code for $encoding.  :-)
  • Well, sure, I explicitly mentioned 'vtables' last time I brought this up. But a single pointer is fairly paltry, as tables go.  :-)
  • I dunno. Perhaps you should be happy that I have a policy of refraining from grumbling about handicapped operating systems.  :-)
  • So I'm thinking about ??, or !!, or //, or \\, or whatever. But I think I like ?? the best so far. Or the least worst.
  • Would you trust the linguistic intuitions of someone who has been studying Latin or Greek for three days?
  • But I know what's important to me, and what isn't. And I think I know what people can get used to, and what they can even learn to like. (It just takes some people longer than others. :-)
  • That being said, I think we should immediately deprecate any string concatenation that combines '19' with '99'.  :-)


  • We don't have enough parallel universes to allow all uses of all junction types--in the absence of quantum computing the combinatorics are not in our favor...
  • I try not to confuse roles and traits in my own life. Being the Perl god is a role. Being a stubborn cuss is a trait.  :-)
  • And in the limiting case where the optimizer is completely broken because it's not implemented yet, we get to work around that too. Optionally...

Source code

Quotations come from the source code to Perl version 4. Some may be present in more recent versions as well.


  • double value; /* or your money back! */
    short changed; /* so triple your money back! */
  • /* now make a new head in the exact same spot */


  • #define NULL 0 /* silly thing is, we don't even use this */
  • #define SIGILL 6 /* blech */
  • if (rsfp = mypopen('/bin/mail root','w')) { /* heh, heh */


  • /* And you'll never guess what the dog had */
    /* in its mouth... */
  • break; /* don't do magic till later */
  • stab_val(stab)->str_nok = 1; /* what a wonderful hack! */
  • tmps_base = tmps_max; /* protect our mortal string */


  • pos += screamnext[pos] /* does this goof up anywhere? */
  • str->str_pok |= SP_FBM; /* deep magic */
    s = (unsigned char*)(str->str_ptr); /* deeper magic */


The Configure script in the Perl source code is generated by a tool called Metaconfig, which was also used in a number of Larry Wall's other programs.

  • echo 'Congratulations. You aren't running Eunice.
  • echo ' don't have Berkeley networking in libc.a...'
    echo 'but the Wollongong group seems to have hacked it in.
  • echo 'ICK, NOTHING WORKED!!! You may have to diddle the includes.';;
  • echo $package has manual pages available in source form.
    echo 'However, you don't have nroff, so they're probably useless to you.
  • echo 'Your stdio isn't very std.'
  • [End of diatribe. We now return you to your regularly scheduled programming...]
  • OOPS! You naughty creature! You didn't run Configure with sh! I will attempt to remedy the situation by running sh for you...
  • That means I'll have to use $ans to suppress newlines now.
    Life is ridiculous.
  • There is, however, a strange, musty smell in the air that reminds me of something...hmm...yes...I've got it...there's a VMS nearby, or I'm a Blit.
  • You can't have filenames longer than 14 chars. You can't even think about them!
  • Your csh still thinks true is false. Write to your vendor today and tell them that next year Configure ought to 'rm /bin/csh' unless they fix their blasted shell. :-)

Other files

  • /* we have tried to make this normal case as abnormal as possible */
    • cmd.c
  • s = (char*)(long)retval; /* ouch */
    • doio.c
  • signal(i, SIG_DFL); /* crunch, crunch, crunch */
    • doarg.c
  • if (instr(buf,sys_errlist[errno])) /* you don't see this */
    • eval.c
  • /* dbmrefcnt--; */ /* doesn't work, rats */
    • hash.c
  • #else /* !STDSTDIO */ /* The big, slow, and stupid way */
    • str.c
  • /* This bit of chicanery makes a unary function followed by a parenthesis into a function with one argument, highest precedence. */
    • toke.c


  • Be consistent.
    • In the perl man page
  • Does the same as the system call of that name. If you don't know what it does, don't worry about it.
    • In the perl man page regarding chroot(2)
  • Even if you aren't in doubt, consider the mental welfare of the person who has to maintain the code after you, and who will probably put parens in the wrong place.
    • In the perl man page
  • Help save the world!
    • In README
  • If you want your program to be readable, consider supplying the argument.
    • In the perl man page
  • In general, they do what you want, unless you want consistency.
    • In the perl man page
  • Okay, that's definitely enough hype.
    • In the perl man page
  • Perl is designed to give you several ways to do anything, so consider picking the most readable one.
    • In the perl man page
  • Remember though that
    • In the perl man page
  • The autodecrement is not magical.
    • In the perl man page
  • *** The previous line contains the naughty word '$&'.\n
    if /(ibm|apple|awk)/; # :-)
    • In the perl man page
  • When in doubt, parenthesize. At the very least it will let some poor schmuck bounce on the % key in vi.
    • In the perl man page

Public Talks

"3rd State of the Onion"

Taken from the transcript of the talk.

  • But I'm not here to talk about postmodernism. I tried to do that last spring, and afterwards I was thoroughly deconstructed by the deconstructionists for attempting to deconstruct deconstructionism. At least, that's the construction I put on their construction of it. I was talking about postmodern culture, and they thought I was talking about postmodern literature. Not at all the same thing!

"Present Continuous - Future Perfect"

Taken from the transcript of the talk.

  • And C was good at something I like to call manipulexity, that is the manipulation of complex things. While shell was good at something else which I call whipuptitude, the aptitude for whipping things up.
  • So... Perhaps the Perl 6 slogan should be "All Your Paradigms Are Belong To Us". We'll get to that.
  • I simultaneously believe that languages are wonderful and awful. You have to hold both of those. Ugly things can be beautiful. And beautiful can get ugly very fast. You know, take Lisp. You know, it's the most beautiful language in the world. At least up until Haskell came along. (laughter) But, you know, every program in Lisp is just ugly. I don't figure how that works.
  • Now, I'm not the only language designer with irrationalities. You can think of some languages to go with some of these things.
    • "We've got to start over from scratch" - Well, that's almost any academic language you find.
    • "English phrases" - Well, that's Cobol. You know, cargo cult English. (laughter)
    • "Text processing doesn't matter much" - Fortran.
    • "Simple languages produce simple solutions" - C.
    • "If I wanted it fast, I'd write it in C" - That's almost a direct quote from the original awk page.
    • "I thought of a way to do it so it must be right" - That's obviously PHP. (laughter and applause)
    • "You can build anything with NAND gates" - Any language designed by an electrical engineer. (laughter)
    • "This is a very high level language, who cares about bits?" - The entire scope of fourth generation languages fell into this... problem.
    • "Users care about elegance" - A lot of languages from Europe tend to fall into this. You know, Eiffel.
    • "The specification is good enough" - Ada.
    • "Abstraction equals usability" - Scheme. Things like that.
    • "The common kernel should be as small as possible" - Forth.
    • "Let's make this easy for the computer" - Lisp. (laughter)
    • "Most programs are designed top-down" - Pascal. (laughter)
    • "Everything is a vector" - APL.
    • "Everything is an object" - Smalltalk and its children. (whispered:) Ruby. (laughter)
    • "Everything is a hypothesis" - Prolog. (laughter)
    • "Everything is a function" - Haskell. (laughter)
    • "Programmers should never have been given free will" - Obviously, Python. (laughter)
  • How do you type it? With your keyboard.

The State of the Onion 10

Taken from The State of the Onion 10

  • If there's a particular problem that Perl is trying to solve, it's the basic fact that all programming languages suck. Sort of the concept of original sin, applied to programming languages.
  • There are a lotta computer languages out there doing drugs.
  • In computer science, it is said that premature optimization is the root of all evil.

The State of the Onion 11

Taken from The State of the Onion 11 ("Programming is Hard. Let's Go Scripting")

  • Suppose you went back to Ada Lovelace and asked her the difference between a script and a program. She'd probably look at you funny, then say something like: Well, a script is what you give the actors, but a program is what you give the audience. That Ada was one sharp lady...
  • I started out as a BASIC programmer. Some people would say that I'm permanently damaged. Some people are undoubtedly right... But I'm not going to apologize for that. All language designers have their occasional idiosyncracies. I'm just better at it than most. :-)
  • But you could do extreme programming. In fact, I had a college buddy I did pair programming with. We took a compiler writing class together and studied all that fancy stuff from the dragon book. Then of course the professor announced we would be implementing our own language, called PL/0. After thinking about it a while, we announced that we were going to do our project in BASIC. The professor looked at us like were insane. Nobody else in the class was using BASIC. And you know what? Nobody else in the class finished their compiler either. We not only finished but added I/O extensions, and called it PL 0.5. That's rapid prototyping.
  • Is LISP a candidate for a scripting language? While you can certainly write things rapidly in it, I cannot in good conscience call LISP a scripting language. By policy, LISP has never really catered to mere mortals... And, of course, mere mortals have never really forgiven LISP for not catering to them.
  • As a linguist, I don't think of Ada as a big language. Now, English and Japanese, those are big languages. Ada is just a medium-sized language.

Larry Wall Speaks at Google (2008)

Video on YouTube.

  • The only reason I've managed to run this open source project, is that I have learned to delegate even the delegation to other people. (final words of the video)


Note: On IRC, Wall uses the nickname "TimToady" (the phonetic equivalent of TIMTOWTDI, which are the initials of the Perl Motto "There is More Than One Way to Do it").

<TimToady>  TimToady's Lament: The pain in reign falls mainly in the 'splain.

Freenode's #perl6 on 26 February, 2007. Source.


  • [Boxed] Multiple bouncing balls in a box are a metaphor for community. Notice how the escaping balls explode. This is what happens to people who move from Perl to Ruby.
  • ...Then you start building things like the Berlin wall to keep people inside your community. In anthropological terms, that's tribalism. A tribal Perl programmer might say, "If you leave the Perl tribe to go and join the Python tribe, we will hunt you down, cook you, and eat you." Or if you join the Ruby tribe, you will explode. By and large, I am not in favor of tribalism. Except for my tribe, of course.
    • ibid.
  • The three chief virtues of a programmer are: Laziness, Impatience and Hubris.
    • From the glossary of the first Programming Perl book
  • The problem with being consistent is that there are lots of ways to be consistent, and they're all inconsistent with each other.
  • There's really no way to fix this and still keep Perl pathologically eclectic.
    • Larry Wall, Tom Christiansen, and Jon Orwant, Programming Perl, third edition, section 3.10

External links

Wikipedia has an article about:

Simple English

Larry Wall is an American programmer, best known for creating the programming language Perl. He worked at NASA for a little bit. He is currently working on a new version of Perl.


Got something to say? Make a comment.
Your name
Your email address