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.)
About this quote
- What does it mean?
- Historically Tcl stored everything as strings, while Perl avoided that from the start.
- In plain terms
- Tcl used string storage; Perl used typed storage early on.
- What can you take from it?
- Design choices affect data handling.
Where it applies
Putting it to work
Questions to consider
- How do storage decisions impact program speed?
Another view
String storage can simplify parsing but hurt efficiency.
More from Larry Wall
Tcl tends to get ported to weird places like routers.
Permalink to quote #135 Just don't make the '9' format pack/unpack numbers... :-)
Permalink to quote #137 It's certainly easy to calculate the average attendance for Perl conferences.
Permalink to quote #134
Related quotes
> (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.
Larry WallLarry Wall quote #51 So far we've managed to avoid turning Perl into APL. :-)
Larry WallLarry Wall quote #72 If you try to solve a hard problem, the question is not whether you will use a powerful enough language, but whether you will (a) use a powerful language, (b) …
Paul GrahamPaul Graham quote #5