46 Larry Wall Quotes on Software

Larry Wall quotes on software

5. I don't know if it's what you want, but it's what you get. :-)

7. 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. :-)

14. It's documented in The Book, somewhere...

17. Let's say the docs present a simplified view of reality... :-)

18. Let us be charitable, and call it a misleading feature :-)

22. The only disadvantage I see is that it would force everyone to get Perl. Horrors. :-)

28. All language designers are arrogant. Goes with the territory... :-)

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

31. Hey, I had to let awk be better at *something*... :-)

34. I think it's a new feature. Don't tell anyone it was an accident. :-)

44. ... an initial underscore already conveys strong feelings of magicalness to a C programmer.

46. : And it goes against the grain of building small tools. Innocent, Your Honor. Perl users build small tools all day long.

49. 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. :-)

64. I want to see people using Perl to glue things together creatively, not just technically but also socially.

81. Tcl long ago fell into the Forth trap, and is now trying desperately to extricate itself (with some help from Sun's marketing department).

93. Anybody want a binary telemetry frame editor written in Perl?

99. The following two statements are usually both true: There's not enough documentation. There's too much documentation.

104. Part of language design is perturbing the proposed feature in various directions to see how it might generalize in the future.

105. Sometimes we choose the generalization. Sometimes we don't.

113. How do Crays and Alphas handle the POSIX problem?

127. 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).

129. switch (ref $@) { OverflowError => warn 'Dam needs to be drained'; DomainError => warn 'King needs to be trained'; NuclearWarError => die; }

132. 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.

151. You don't have to wait--you can have it in 5.004_54 or so. :-)

153. It's not really a rule--it's more like a trend.

155. The code also assumes that it's difficult to misspell 'a' or 'b'. :-)

159. Think of prototypes as a funny markup language--the interpretation is left up to the rendering engine.

160. 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.

163. I suppose one could claim that an undocumented feature has no semantics. :-(

171. Portability should be the default.

174. Almost nothing in Perl serves a single purpose.

177. 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.

188. 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 CGI.pm, we're probably okay.

198. 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. :-)

210. I dunno. Perhaps you should be happy that I have a policy of refraining from grumbling about handicapped operating systems. :-)

217. One operator is no big deal. That can be fixed in a jiffy.

222. Orthogonality for orthogonality's sake is not something I'm keen on.

225. That is a known bug in 5.00550. Either an upgrade or a downgrade will fix it.

236. double value; /* or your money back! */ short changed; /* so triple your money back! */

242. break; /* don't do magic till later */

270. In general, they do what you want, unless you want consistency.

285. In computer science, it is said that premature optimization is the root of all evil.

300. It is easier to port a shell than a shell script.

304. : 1. What is the possibility of this being added in the future? In the near future, the probability is close to zero. In the distant future, I'll be dead, and posterity can do whatever they like... :-)

308. May you do Good Magic with Perl.

313. Many computer scientists have fallen into the trap of trying to define languages like George Orwell's Newspeak, in which it is impossible to think bad thoughts. What they end up doing is killing the creativity of programming.