<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> I don't know for certain, since I fled Perl for good a decade ago. I do know that, 20 years ago, processing stream input from various sources with a regexp tended to be a short one-liner in Perl. We're really in Perl's home turf when doing things like that, and the terseness one can get with some CPAN modules is scary. Options I see are: (1) avoid using examples that are Perl-one-liners; (2) emphasize readability/maintainability if you're going to do the Perl-one-liner examples anyway; (3) design a text-processing #lang that's no more than 2x the verbosity of Perl on Perl-one-liners, and use that. Personally, I would go with #1. #3 would be fun to design, but would probably be one of those Scheme curiosities that is never used by more than one or two people, which is not the tradition of PLT. Robby Findler wrote at 05/26/2010 09:28 AM: <blockquote cite="mid:AANLkTinnuF4yGT9HRsBTg89_FYPaAMRmLwe0PzAeFFcm@mail.gmail.com" type="cite"> <pre wrap="">On Tuesday, May 25, 2010, Neil Van Dyke <a class="moz-txt-link-rfc2396E" href="mailto:neil@neilvandyke.org"><neil@neilvandyke.org></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Regarding single-character identifiers... Given that Scheme standard identifiers tend to be verbose, and that many of these examples squeezed into 40x7 are one-liners in Perl anyway, maybe focusing on readability is a good idea. Maybe bump it up to as wide as 70x7. </pre> </blockquote> <pre wrap=""> How many of the current set really are one-liners in perl? (not that I really want to delve too deeply into this question but I also don't want the page to look stupid to perl folk) </pre> </blockquote> </body> </html>