Comments for As Thick As Two Short Planks - Mark Fowler's Blog http://blog.twoshortplanks.com Tue, 03 Nov 2009 01:25:59 +0000 http://wordpress.com/ hourly 1 Comment on Introducing XML::Easy by john napiorkowski http://blog.twoshortplanks.com/2009/11/02/introducing-xmleasy/#comment-86 john napiorkowski Tue, 03 Nov 2009 01:25:59 +0000 http://blog.twoshortplanks.com/?p=126#comment-86 I'll be sure to give it a try! I’ll be sure to give it a try!

]]> Comment on CPAN Unplugged by 2shortplanks http://blog.twoshortplanks.com/2009/10/12/cpan-unplugged/#comment-58 2shortplanks Wed, 14 Oct 2009 12:43:40 +0000 http://blog.twoshortplanks.com/?p=101#comment-58 Of course, modern minicpan (updated some time after you wrote this script) now uses Keep-Alive, so it's really just one TCP stream Of course, modern minicpan (updated some time after you wrote this script) now uses Keep-Alive, so it’s really just one TCP stream

]]> Comment on CPAN Unplugged by Matt S Trout http://blog.twoshortplanks.com/2009/10/12/cpan-unplugged/#comment-57 Matt S Trout Wed, 14 Oct 2009 07:12:23 +0000 http://blog.twoshortplanks.com/?p=101#comment-57 http://www.trout.me.uk/perl/mirror.sh.txt is my take on the process. Slightly crazier but does the sync in two rsync calls rather than oh-my-gods-how-many HTTP calls. -- mst, out. http://www.trout.me.uk/perl/mirror.sh.txt

is my take on the process. Slightly crazier but does the sync in two rsync calls rather than oh-my-gods-how-many HTTP calls.

– mst, out.

]]> Comment on say What? by 2shortplanks http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-48 2shortplanks Wed, 07 Oct 2009 13:37:34 +0000 http://blog.twoshortplanks.com/?p=90#comment-48 @wallace: What? @wallace: What?

]]> Comment on say What? by 2shortplanks http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-47 2shortplanks Wed, 07 Oct 2009 13:36:53 +0000 http://blog.twoshortplanks.com/?p=90#comment-47 I've always disliked -l because it means that *everything* I print has a newline by default. Realistically, most times I tend to do several prints with a post if, and then a final say to avoid having to use a tertiary operator too much. Of course, in the convoluted blog entry that wasn't clear... I’ve always disliked -l because it means that *everything* I print has a newline by default. Realistically, most times I tend to do several prints with a post if, and then a final say to avoid having to use a tertiary operator too much.

Of course, in the convoluted blog entry that wasn’t clear…

]]> Comment on say What? by Dave Cross http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-46 Dave Cross Tue, 06 Oct 2009 19:43:15 +0000 http://blog.twoshortplanks.com/?p=90#comment-46 perl -e 'print 235*1.15, "\n"' Did you really use that? Did no-one ever introduce you to the -l command line option? perl -le 'print 235*1.15' Still not as short as the 5.10 version, but you've been wasting a lot of keystrokes under 5.8.8 :-) perl -e ‘print 235*1.15, “\n”‘

Did you really use that? Did no-one ever introduce you to the -l command line option?

perl -le ‘print 235*1.15′

Still not as short as the 5.10 version, but you’ve been wasting a lot of keystrokes under 5.8.8 :-)

]]> Comment on say What? by wallace http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-45 wallace Tue, 06 Oct 2009 11:41:58 +0000 http://blog.twoshortplanks.com/?p=90#comment-45 say what one more time. i dare you! say what one more time. i dare you!

]]> Comment on say What? by Sol http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-44 Sol Tue, 06 Oct 2009 11:24:51 +0000 http://blog.twoshortplanks.com/?p=90#comment-44 I really scoffed at "say" when I first heard about it, but after nine months of Perl 6 programming I can say I was completely wrong about that. <code>say $value;</code> really is a lot nicer than <code>print "$value\n";</code>. And it's even more drastic if you are calculating something you'd like to print without saving: <code>say @values.sort.perl;</code> is much cleaner than <code>print "{@values.sort.perl}\n";</code>. (Is there even a way to do that in one statement in Perl 5?) I really scoffed at “say” when I first heard about it, but after nine months of Perl 6 programming I can say I was completely wrong about that. say $value; really is a lot nicer than print "$value\n";. And it’s even more drastic if you are calculating something you’d like to print without saving: say @values.sort.perl; is much cleaner than print "{@values.sort.perl}\n";. (Is there even a way to do that in one statement in Perl 5?)

]]> Comment on say What? by Moritz Onken http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-43 Moritz Onken Tue, 06 Oct 2009 08:27:34 +0000 http://blog.twoshortplanks.com/?p=90#comment-43 Too bad that apple shipped perl 5.10.0 with the unknown error bug... Too bad that apple shipped perl 5.10.0 with the unknown error bug…

]]> Comment on say What? by Rhomboid http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-42 Rhomboid Mon, 05 Oct 2009 22:42:23 +0000 http://blog.twoshortplanks.com/?p=90#comment-42 Seriously? You could have just used perl -le 'print 235*1.15' ...with perl 5.8. Seriously? You could have just used

perl -le ‘print 235*1.15′

…with perl 5.8.

]]>