Dan Sugalski writes:
: Unless Larry says otherwise, this:
:
:my num @foo;
:
: will have the data portion of the @foo PMC point off to a block of memory
: with floats jammed end-to-end in it.
I'm not going to say other.
Larry
Nick Ing-Simmons writes:
: Larry Wall <[EMAIL PROTECTED]> writes:
: >I think using overloading to write a parser is going to be a relic of
: >Perl 5's limitations, not Perl 6's.
:
: I am _NOT_ using overloading to write a parser.
: Parse::Yapp is just fine for writing parsers. I am trying to re-
Dan Sugalski writes:
: Resizing the vtable at runtime is a really dodgy thing. There are some
: rather huge threading implications here--changing their size (as opposed to
: using up a limited number of "uncommitted" spots we leave at the end) means
: potentially having to move all the vtables
On Tue, 24 Apr 2001 19:17:08 -0500, Jarkko Hietaniemi wrote:
>Wasn't Perl also taken, so why care...? I vaguely remember reading
>about another language called PERL...
It was "Pearl", AFAIK. That's why the "a" got missing. So I've been
told... ("Practical Extracting And Reporting Language"... y
On Tue, Apr 24, 2001 at 08:11:01PM -0400, Andy Dougherty wrote:
> On Tue, 24 Apr 2001, Dan Sugalski wrote:
>
> > The big reason for Parrot was that I was terribly amused by Simon's joke,
> > and I have visions of releasing perl 6.0 on April 1 next year... :)
> >
> > Other than that, I really do
On Tue, 24 Apr 2001, Dan Sugalski wrote:
> The big reason for Parrot was that I was terribly amused by Simon's joke,
> and I have visions of releasing perl 6.0 on April 1 next year... :)
>
> Other than that, I really don't care much, though a good (or bad) pun is
> always a big plus.
Starting
Uri Guttman wrote:
> i was looking at dan's PMC arena allocator struct and it reminded me of
> something an older language can do (which MJD has likened to an early
> perl :). ever heard of AREA in PL/I? it was a large chunk of ram
> dedicated to allocate memory from. what was special is that all
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> Other than that, I really don't care much, though a good (or bad)
DS> pun is always a big plus.
how about 'perm' which is 'perl'++
uri
--
Uri Guttman - [EMAIL PROTECTED] -- http://www.sysarch.com
SYStems ARCH
At 03:46 PM 4/24/2001 -0400, NeonEdge wrote:
>Actually, there are already languages named 'Parrot' and 'Poly' (links
>below). Besides, I'm getting tired of animals . What about something
>more fun, like "Magoo" or "Gilligan"? Or maybe we could move to insects, like
>"Mantis" or "Wasp".
The bi
At 12:00 PM 4/24/2001 -0400, Dan Sugalski wrote:
>I've updated http://www.sidhe.org/~dan/perl/gc.html (as well as html-izing
>it. The text version's still there) for those who are curious.
>Specifically the implementation section for reference tracking and the PMC
>arena stuff's done.
Y'know,
Actually, there are already languages named 'Parrot' and 'Poly' (links
below). Besides, I'm getting tired of animals . What about something
more fun, like "Magoo" or "Gilligan"? Or maybe we could move to insects, like
"Mantis" or "Wasp".
If we have to go with an animal, though, I like "Buzza
On Tue, 24 Apr 2001, Dan Sugalski wrote:
> Or, rather, I think we should have one. Naming the interpreter separate
> from the language may help folks keep the various bits separate in their
> minds. (It'll certainly help me be clearer when I talk about it)
>
> Personally, I'm up for calling the i
I've updated http://www.sidhe.org/~dan/perl/gc.html (as well as html-izing
it. The text version's still there) for those who are curious.
Specifically the implementation section for reference tracking and the PMC
arena stuff's done.
If folks would care to look and comment, that'd be keen. Bet
At 12:35 PM 4/24/2001 -0300, Branden wrote:
>At 11:27 AM 24/04/2001 -0400, Dan Sugalski wrote:
>>Or, rather, I think we should have one. Naming the interpreter separate
>>from the language may help folks keep the various bits separate in their
>>minds. (It'll certainly help me be clearer when I
At 11:27 AM 24/04/2001 -0400, Dan Sugalski wrote:
>Or, rather, I think we should have one. Naming the interpreter separate
>from the language may help folks keep the various bits separate in their
>minds. (It'll certainly help me be clearer when I talk about it)
Actually, I think the language
Or, rather, I think we should have one. Naming the interpreter separate
from the language may help folks keep the various bits separate in their
minds. (It'll certainly help me be clearer when I talk about it)
Personally, I'm up for calling the interpreter "Parrot" unless someone has
an object
Apologies all...I have the document, but I'm having trouble getting it out
of my computer. I don't have Internet access yet and my floppy drive is
refusing to read. I'll see if I can get the printer hooked up tonight,
print the thing out, retype it at work tomorrow, and send it in then.
Dave
Larry Wall <[EMAIL PROTECTED]> writes:
>Nick Ing-Simmons writes:
>: >You really have to talk about overloading boolean context
>: >in general.
>:
>: Only if you are going to execute the result in the normal perl realm.
>: Consider using the perl parser to build a parse tree - e.g. one to
>: read
Well, generally, I try to keep my mouth shut and stay out of these
kinds of things, but I'd really like to see some more discussion on
this one. So, ...
It's not a wacko idea, imho; in fact, it could also work quite well
with a "Stop-and-Copy" semispaces-type GC, if Dan elects to go with
somethi
19 matches
Mail list logo
