Re^2: Why should I use perl 5.10?

Well, it has the say builtin.

and

Admitted, doesn't sound really great,

this is exactly my opinion too, say() doesn't say anything about its use ;-)

Wouldn't even println() have been a better naming choice? (BYMMV) ;-)

  ...
  {
   local $\ = "\n";
   ...
   ...
   print $foo;
   ...
  }
[download]

Regards

mwa

Comment on Re^2: Why should I use perl 5.10? Download Code

Replies are listed 'Best First'.
Re^3: Why should I use perl 5.10? by moritz (Cardinal) on Nov 30, 2007 at 10:31 UTC
Wouldn't even println() have been a better naming choice? Surely not! Perl builtins tend to be one word that can (syntactically) be read as plain English, with a few exceptions that come from POSIX system calls (like gethostbyname) And `println` is too long, compared to `say` ;-) The word `say` suggests some I/O similar to print, which in fact it is. The exact semantics are not obvious, but they aren't hard to learn.	[reply] [d/l] [select]
Re^4: Why should I use perl 5.10? by blazar (Canon) on Dec 01, 2007 at 15:44 UTC
And `println` is too long, compared to `say` ;-) I personally believe that this is serious enough not to warrant a ;-) since the keyword is huffmanization. IME I tend to `print ... "\n"` just as often or more than in `"\n"`-less form so in oneliners and minimal example scripts I tend to use `-l` quite a lot. But that is bad and risky in that as sometimes it pops up, it can interact with modules that do actual prints. And module authors probably should not be concerned with setting `local $\` accordingly. So for all these reasons and for the others that have been said here thus far, however simple it is `say()` is welcome, and a blessing!	[reply] [d/l] [select]
Re^5: Why should I use perl 5.10? by BrowserUk (Patriarch) on Dec 02, 2007 at 00:49 UTC
And module authors probably should not be concerned with setting local $\ accordingly. They are exactly the people who should be concerned with it. They are making assumptions about the environment in which they will run, which is not theirs to dictate. But overall, I welcome say. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^6: Why should I use perl 5.10? by blazar (Canon) on Dec 02, 2007 at 12:41 UTC
Re^7: Why should I use perl 5.10? by BrowserUk (Patriarch) on Dec 02, 2007 at 13:08 UTC
Some notes below your chosen depth have not been shown here
Re^3: Why should I use perl 5.10? by Anonymous Monk on Dec 01, 2007 at 02:16 UTC
I don't understand why we didn't just use puts(). NIH?	[reply]
Re^4: Why should I use perl 5.10? by chromatic (Archbishop) on Dec 01, 2007 at 03:33 UTC
That's easy: because `puts` is a stupid name. Why continue the confusion that C has already `creat`d?	[reply] [d/l] [select]


Think about Loose Coupling
	PerlMonks