Re: [PATCH: perl@7674] updates to README.os390

2000-11-14 Thread Jarkko Hietaniemi
> One of the warnings seen in copious quantities seemed to be this one: > > Malformed UTF-8 character (0 byte, need 2) at op/bop.t line 139. > Malformed UTF-8 character (0 byte, need 2) at op/bop.t line 139. That's a definite sign something that shouldn't be calling utf8_to_uv() is: 0 bytes (m

Re: [ID 20001114.002] Code-Cleanups concerning SOCKS5 and Solaris

2000-11-14 Thread Nick Ing-Simmons
Jens Hamisch <[EMAIL PROTECTED]> writes: > >I started from APC 7680. The asserts were already defined. I guessed as much. > > >> I dislike the >> >> ! #if defined(sun) && !defined(_LP64) >> >> even more ! >> >> Sun in _LP64 mode should be handled by the Configure stuff - as I understand >> i

Why "" for false?

2000-11-14 Thread Mark-Jason Dominus
Prior to Perl 5.000, the return value from the == operator was 1 for true and 0 for false. Starting in Perl 5.000, the resturn value for false comparisons was no longer 0; it was instead "". Does anyone remember why this change was made? Mark-Jason Dominus

Re: [ID 20001114.001] use utf8;use charnames; is incorrect for \x{80}-\x{FF}

2000-11-14 Thread Simon Cozens
On Wed, Nov 15, 2000 at 03:06:19AM +1300, Andrew McNaughton wrote: > On Tue, 14 Nov 2000, Nick Ing-Simmons wrote: > > Andrew McNaughton <[EMAIL PROTECTED]> writes: > > >use utf8; > > >use charnames ':full'; > > >$text .= "\N{LATIN CAPITAL LETTER A WITH DIAERESIS}"; > > > > > > > > >This fails beca