Glenn, et.al.
I'm going to be combining a number of different comments in here.
Glenn Linderman wrote:
> I was surprised by the read/write operations, but have no objection to them.
> New/get/set and the individual data member access functions are the critical
> pieces, as the I/O could be done
Original Message
Subject: Re: Sublist auto*
Date: Sat, 05 Aug 2000 14:39:33 -0400
From: Edwin Wiles <[EMAIL PROTECTED]>
Organization: Totally Disorganized
To: Johan Vromans <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Johan Vromans wrote:
Of all the variations that I've seen so far (I'm way behind on reading
the list), the one I like the best is:
qc{ multi
line
comment
here }
Second best, but still acceptable would be:
#<# variations just don't seem "perlish" to me. Sorry!
That's just a personal feeling.
If you just have to g
John Porter wrote:
>
> Michael Mathews wrote:
> > Using a two-character syntax to start and end a multiline comment seems to
> > be a good way to satisfy both the desired similarity to "#" and the desired
> > uniqueness to avoid collision with real single-line quotes. I would suggest
> > a (# man
o I've
probably made mistakes there too.
Be kind. If you can't be kind, then at least be polite?
Here Goes!
=head1 TITLE
Enhanced Pack/Unpack
=head1 VERSION
Maintainer: Edwin Wiles <[EMAIL PROTECTED]>
Date: 1 Aug 2000
Version: DRAFT - Not
Theoretically, we do have a list now. I'm going to try using it. It's
also a personal experiment, since I'm subscribed to 'all', but not to
'language'.
I've already thrown a few notes together for a perl5 module, but nothing
I'm ready to share just yet. I need to dig through CPAN to make sure
