Re: This is a test message

2001-01-16 Thread Bart Lateur
On Mon, 15 Jan 2001 18:30:29 -0800, Vicki Brown wrote: >We are in the process of moving the mailing lists to perl.org. Is that why the new messages (like the Disgest::MD5 module announcement) don't have the "[MacPerl]" string in the subject? -- Bart.

sysread . . 4096?

2001-01-16 Thread John Delacour
Can someone please explain why 2^12 is seen so often as the chunk size in perl scripts? Is there some UNIX reason for this number that really doesn't figure in the Mac environment? I find it more useful to read as large a chunk as the memory will sensibly allow. Do I lose anything by reading

Re: sysread . . 4096?

2001-01-16 Thread Bill Becker
It USED to be the default block size for storage devices dating all the way back to when mainframes were the only thing around. It is also mostly a page size for a vast majority of vitual memory computing environments. Crossing a page boundary was sometimes a painful thing to do, especially whe

[MacPerl] || vs or in CGI.pm

2001-01-16 Thread Scott R. Godin
fails: my $GameType = param('mapstyle') or $default_mapstyle; works: my $GameType = param('mapstyle') || $default_mapstyle; Am I mistaken in assuming that "I should use 'or' because this is 'string values'" or does this happen "simply because the possibility of returning undef exists in the e

Re: [MacPerl] || vs or in CGI.pm

2001-01-16 Thread Craig S. Cottingham
On 1/16/01 22:49, Scott R. Godin at [EMAIL PROTECTED] wrote: > fails: > my $GameType = param('mapstyle') or $default_mapstyle; > > works: > my $GameType = param('mapstyle') || $default_mapstyle; According to perlop: [ ... ] left|| [ ... ] right = += -= *= etc.