Steve Fink <[EMAIL PROTECTED]> wrote:
> On Sep-01, Leopold Toetsch wrote:
>> Below is a pod document describing some IMHO worthwhile changes. I hope
>> I didn't miss some issues that could inhibit the implementation.
> Overall, I like it, although I'm sure I haven't thought of all of the
> repercu
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 5:17 PM +0200 9/1/04, Leopold Toetsch wrote:
>>Below is a pod document describing some IMHO worthwhile changes. I
>>hope I didn't miss some issues that could inhibit the implementation.
> Okay, the "No" warrants more explanation.
Thanks.
> First off,
At 5:17 PM +0200 9/1/04, Leopold Toetsch wrote:
Below is a pod document describing some IMHO worthwhile changes. I
hope I didn't miss some issues that could inhibit the implementation.
Okay, the "No" warrants more explanation.
First off, the current structure of PMCs, Buffers, and Strings is
defi
On Sep-01, Leopold Toetsch wrote:
> Below is a pod document describing some IMHO worthwhile changes. I hope
> I didn't miss some issues that could inhibit the implementation.
Overall, I like it, although I'm sure I haven't thought of all of the
repercussions.
The one part that concerns me is the
On Wed, Sep 01, 2004 at 05:17:55PM +0200, Leopold Toetsch wrote:
> PMCs are using too much memory (5 words for an Integer PMC, 11 + n
> words plus two indirection for an object with n attributes). The
> reduction of IIRC 9 words to the current 5 words almost doubled
> execution speed for not too s
On Wed, 2004-09-01 at 11:17, Leopold Toetsch wrote:
> Comments welcome,
Honestly, much of this goes beyond my meager understanding of Parrot
internals, but I've read it, and most of it seems reasonable. Just on
point where you may not have considered a logical alternative:
> =head2 2.6. Morphing
At 5:17 PM +0200 9/1/04, Leopold Toetsch wrote:
Below is a pod document describing some IMHO worthwhile changes. I
hope I didn't miss some issues that could inhibit the implementation.
Interesting. But... no. Things are the way they are on purpose -- a
lot of thought, a not-incosiderable amount o
Below is a pod document describing some IMHO worthwhile changes. I hope
I didn't miss some issues that could inhibit the implementation.
Comments welcome,
leo
=head1 1. Proposal for a new PMC layout and more
=head2 1.1. Current state - PMC size and structure
PMCs are using too much memo
