Comments on: say What? http://blog.twoshortplanks.com/2009/10/05/say-what/ Tue, 03 Nov 2009 01:25:59 +0000 http://wordpress.com/ hourly 1 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?

]]> 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…

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

]]> 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!

]]> 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?)

]]> 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…

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

]]> By: Hinrik Örn Sigurðsson http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-41 Hinrik Örn Sigurðsson Mon, 05 Oct 2009 22:40:39 +0000 http://blog.twoshortplanks.com/?p=90#comment-41 Too bad you didn't know about the -l option, which turns causes "print" to append a newline. :) I.e. "perl -MSomeModule -le 'print SomeModule->VERSION'" The "say" version is still an improvement though, key stroke-wise. Too bad you didn’t know about the -l option, which turns causes “print” to append a newline. :)

I.e. “perl -MSomeModule -le ‘print SomeModule->VERSION’”

The “say” version is still an improvement though, key stroke-wise.

]]> By: Jakub Narębski http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-40 Jakub Narębski Mon, 05 Oct 2009 22:25:25 +0000 http://blog.twoshortplanks.com/?p=90#comment-40 Simply use '-l' switch: <code> bash$ perl -le 'print 235*1.15' </code> Simply use ‘-l’ switch:

bash$ perl -le 'print 235*1.15'

]]> By: Chas. Owens http://blog.twoshortplanks.com/2009/10/05/say-what/#comment-39 Chas. Owens Mon, 05 Oct 2009 21:23:46 +0000 http://blog.twoshortplanks.com/?p=90#comment-39 Why in the world weren't you saying <code>ssh me@remote "perl -MSomeModule -le 'print SomeModule->VERSION'"</code> Or even better yet <code>ssh me@remote perl -MSomeModule=99999999</code> That will get you an error message like <code>Carp version 99999999 required--this is only version 1.04 at /usr/share/perl/5.8/Exporter/Heavy.pm line 107. BEGIN failed--compilation aborted.</code> Which has the version number in it (in this case Carp is version 1.04) Why in the world weren’t you saying

ssh me@remote "perl -MSomeModule -le 'print SomeModule->VERSION'"

Or even better yet

ssh me@remote perl -MSomeModule=99999999

That will get you an error message like

Carp version 99999999 required--this is only version 1.04 at /usr/share/perl/5.8/Exporter/Heavy.pm line 107.
BEGIN failed--compilation aborted.

Which has the version number in it (in this case Carp is version 1.04)

]]>