On Mon, Apr 16, 2001 at 02:49:07PM -0500, Jarkko Hietaniemi wrote:
> I don't get it.
>
> The first and foremost duty of Perl 6 is to parse and execute Perl 6.
> If it doesn't, it's not Perl 6. I will call this the Prime Directive.
Great, but don't loose sight of the fact that a key feature of "
On Mon, 16 Apr 2001 10:29:41 PDT, Jeff Okamoto <[EMAIL PROTECTED]> wrote:
> > The
> > timescales of corporations like Sun are not the same as those commonly
> > encountered in the open software arena.
>
> Ditto for HP.
Which is more extreme (HP9000/L1000, HP-UX 11.00 + March 2001 patches):
% /u
Tim Bunce wrote:
> If the file doesn't start with Perl 6 thingy then
> it's Perl 5. Period.
To mandate the impossible is to mandate failure.
"Nothing can parse perl like Perl."
Why is that?
> My reading of Larry's comments is that it won't be "in" our "new
> beautiful code". [Umm, pride bef
On Tue, Apr 17, 2001 at 09:23:56AM -0400, John Porter wrote:
> "Nothing can parse perl like Perl."
Just saying it doesn't make it true, you know.
--
Keep the number of passes in a compiler to a minimum.
-- D. Gries
At 10:16 AM 4/17/2001 +0100, Tim Bunce wrote:
>On Mon, Apr 16, 2001 at 02:49:07PM -0500, Jarkko Hietaniemi wrote:
> > People seem to think that telling Perl 5 apart from Perl 6 is trivial.
>
>My reading of Larry's comments is that it will be _made_ trivial at the
>file scope level. If the file doe
Okay, I need some volunteers to write some PDDs. Specifically on these topics:
*) Debugging support perl 6 will or should provide
*) Unicode string handling
*) Safe mode (or some other sandbox scheme) and taint handling
Takers? You don't necessarily have to generate the ideas--a call for
sugges
I'd be interested in taking a part!
My documentation is fairly good, and I think my perl, general development
vocabulary should be good enough to put them together.
I'm sure I'll get some help if needed, right?
:)
Soyoung
-Original Message-
From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
At 10:44 AM 4/17/2001 -0700, Soyoung Park wrote:
>I'd be interested in taking a part!
>
>My documentation is fairly good, and I think my perl, general development
>vocabulary should be good enough to put them together.
>I'm sure I'll get some help if needed, right?
Keen. Which one do you want res
> > > The
> > > timescales of corporations like Sun are not the same as those commonly
> > > encountered in the open software arena.
> >
> > Ditto for HP.
>
> Which is more extreme (HP9000/L1000, HP-UX 11.00 + March 2001 patches):
>
> % /usr/contrib/bin/perl -v
>
> This is perl, version 4.0
>
Dan Sugalski writes:
: At 10:16 AM 4/17/2001 +0100, Tim Bunce wrote:
: >On Mon, Apr 16, 2001 at 02:49:07PM -0500, Jarkko Hietaniemi wrote:
: > > People seem to think that telling Perl 5 apart from Perl 6 is trivial.
: >
: >My reading of Larry's comments is that it will be _made_ trivial at the
: >
On Tue, Apr 17, 2001 at 09:23:56AM -0400, John Porter wrote:
> Tim Bunce wrote:
> > If the file doesn't start with Perl 6 thingy then
> > it's Perl 5. Period.
>
> To mandate the impossible is to mandate failure.
>
> "Nothing can parse perl like Perl."
>
> Why is that?
Because perl has a bunch
I'd like to follow up closely (as well as I can) on all three, but my
biggest interest lies on 'Unicode string handling' because I'm interested in
i18n/l10n stuff!
:)
Do let me know how I can help out.
Soyoung
*) Debugging support perl 6 will or should provide
*) Unicode string handling
*) Sa
Uri Guttman wrote:
> malloc normally doesn't care about alignment.
I'll think you will find it does care.
Alan Burlison
At 09:05 PM 4/17/2001 +0100, Alan Burlison wrote:
>Uri Guttman wrote:
>
> > malloc normally doesn't care about alignment.
>
>I'll think you will find it does care.
I'm pretty sure that everyone's malloc returns data aligned to the CPU's
favorite boundary. It's what we do with the malloc'd area t
14 matches
Mail list logo
