Juergen Boemmels wrote:
> Leopold Toetsch wrotes:
>
> > We currently have constant Key and Sub PMCs both created from the
> > packfile at load time. They live in the constant_table pointing to a
> > constant PMC pool. But we need more.
> >
> > We have allover the core code like this:
> >
> >st
James Michael Dupont <[EMAIL PROTECTED]> wrote:
> Dear fellow hackers,
> First of all, I would like to say that I hope that you dont take
> offence at my silly questions and crazy ideas! ;)
There are no silly questions, only silly answers and crazy ideas are the
motor of development - trying to a
The Perl 6 Summary for the week ending 20030824
Another week, another Perl 6 summary. I'm running late writing this and
I don't care because I spent the bank holiday weekend at a folk festival
and didn't get back 'til Monday evening.
Predictably enough, we'll start with the shenani
Dear fellow hackers,
First of all, I would like to say that I hope that you dont take
offence at my silly questions and crazy ideas! ;)
I have been looking in the amazing work that you have been doing with
parrot and the work that Michal Wallace has been doing with the Pirate,
the following quest
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>> this is only useful if a hashlookup is fast compared with
>> string_make.
>
> Well, it might be. Hashing can be quite fast, ya know.
>
> Here's a better idea, one you'll have more difficulty arguing with --
> imagine a debugger, written in parrot.
>
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
[ snip ]
> * const_string_from_cstring - return cached constant string or create one
> * const_key_new_cstring - return cached PMC or create a constant PMC
Some more thoughts WRT this issue:
- PerlHash isn't suitable for storing/lookup these STRINGs/Key
