I think the octal number representation should not be accepted...
Adam Krolnik
Verification Mgr.
LSI Logic Corp.
Plano TX. 75074
Yes, while still allowing an explicit A()->B(), of course.
I just meant that A->B means A::->B(), or, if you would, "A"->B().
But A()->B would not change in meaning.
--tom, posting blind(ly)
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is int
On Sat, 23 Sep 2000 04:20:37 -0400 (EDT), Philip Newton wrote:
>On Thu, 21 Sep 2000, Tom Christiansen wrote:
>
>> =item perl6storm #0035
>>
>> Make A->B place A in string context, like => does.
>> That way no A()->B naughtiness.
>
>While still allowing explicit A()->B?
Of course. You can still
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0035
>
> Make A->B place A in string context, like => does.
> That way no A()->B naughtiness.
While still allowing explicit A()->B?
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On Fri, 22 Sep 2000, Greg Boug wrote:
> > > =item perl6storm #0064
> > >
> > > Do something about microsoft's CRLF abomination.
>
> Perhaps somehow allowing $/ to take multiple input delimeters (perhaps in a
> fashion similar to egrep)... How about:
[snip]
> $/ = "seperator1|seperator2"
> while () {
> s/^M$//;
> # Process $_
> }
Cute psuedocode.
I don't like at all, it makes me feel like I'm dealing with a
typewritter. But, giving multiple values to $/ seems more painful to me
that to just
tr/\r//d;
on any suspected M$ strings
> > =item perl6storm #0064
> >
> > Do something about microsoft's CRLF abomination.
>
> I think for the case of Microsoft C++ used for the Win32 port, everyone
> would be happy if Perl's sysopen, sysread, etc. did not require binmode.
> Unfortunately, Microsoft made the decision very early on in i
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> At 05:35 PM 9/21/00 -0400, Uri Guttman wrote:
>> i proposed some of that in my rfc47 (universal async i/o). at the perl
>> level you need a delivery interface as with events.
DS> I'm not really worried about the perl level for th
At 05:35 PM 9/21/00 -0400, Uri Guttman wrote:
> > "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> DS> I would *really* like perl's I/O system to do async reads and
> DS> writes to disk files whenever possible. That'd let us get another
> DS> burst of speed in some spots, particularl
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> I would *really* like perl's I/O system to do async reads and
DS> writes to disk files whenever possible. That'd let us get another
DS> burst of speed in some spots, particularly when slurping through
DS> files sequentially (which
At 10:22 AM 9/21/00 -0500, Fisher Mark wrote:
> > =item perl6storm #0064
> >
> > Do something about microsoft's CRLF abomination.
>
>I think for the case of Microsoft C++ used for the Win32 port, everyone
>would be happy if Perl's sysopen, sysread, etc. did not require binmode.
>Unfortunately, Mic
Tom Christiansen <[EMAIL PROTECTED]> wrote:
>=item perl6storm #0016
>
>object as scope/namespace? see python. it's danged clean
>there in that you can now implement safe trivially.
>don't have to keep inventing crazy overloads.
>
Yes, this would be great!
>=item perl6storm #0025
>
>Make -T t
> =item perl6storm #0064
>
> Do something about microsoft's CRLF abomination.
I think for the case of Microsoft C++ used for the Win32 port, everyone
would be happy if Perl's sysopen, sysread, etc. did not require binmode.
Unfortunately, Microsoft made the decision very early on in its C/C++
dev
=item perl6storm #0106
Safe "signals"! (not syssigs,really)
=head1 NAME
perl6storm - tchrist's brainstorm list for perl6
=head1 DESCRIPTION
I'm going away for a long, long time, way past the RFC deadline.
Here is my file of notions I've brainstormed over the last few
weeks. Some have been covered in other RFCs. Many haven't.
15 matches
Mail list logo
