Re^6: One to one file output idiom

After second thought ...

It's "slurp" - eating noisily - which is the misnomer.

To gulp would be a more accurate description for devouring a whole file.

Spew would fit then.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

Comment on Re^6: One to one file output idiom

Replies are listed 'Best First'.
Re^7: One to one file output idiom by haukex (Archbishop) on Jan 17, 2020 at 08:03 UTC
FWIW, Path::Class::File and IO::Any also use "`spew`" (old versions of the File::Slurp docs used the term as well); Mojo::File uses "`spurt`". I think all of these method names are not meant to be taken 100% seriously `;-)` (I also found IO::Barf, if you like it more direct)	[reply] [d/l] [select]
Re^8: One to one file output idiom by LanX (Saint) on Jan 17, 2020 at 14:03 UTC
As I said, I think "slurp" is the culprit here. I'm fine with "spew" cause it's a general term. The "vomit" meaning is limited to human context, like in "to make someone spew". > I think all of these method names are not meant to be taken 100% seriously ;-) Yes, but wrong associations can lead to hard to debug misunderstandings. For instance `wantarray` is true in "list" context. This function should have been named wantlist() instead. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]


laziness, impatience, and hubris
	PerlMonks