On Wed, 6 Sep 2000, Bart Lateur wrote:
Those are not the semantics of print. It returns true (1) if successful, and
false (undef) otherwise. You cannot change that. If I write print "0", it
bloody well shan't be returning false.
Oh, why not? Does anybody actually *ever* check the
On Fri, 8 Sep 2000 01:18:19 -0700 (PDT), Ask Bjoern Hansen wrote:
I really don't understand why you want to have what's printed.
It is handy, sometimes.
But I do think that the overhead of creating a longish string every time
you print something, which is then simply discarded, is not really
"ABH" == Ask Bjoern Hansen [EMAIL PROTECTED] writes:
Oh, why not? Does anybody actually *ever* check the return value of
print? I think it's not as if we'd break a lot of code.
ABH uh, what? you don't do much socket programming now, do you? sockets
ABH breaks all the time. Disks runs out of
On 8 Sep 2000, Chaim Frenkel wrote:
Oh, why not? Does anybody actually *ever* check the return value of
print? I think it's not as if we'd break a lot of code.
ABH uh, what? you don't do much socket programming now, do you? sockets
ABH breaks all the time. Disks runs out of space while
