Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> According to Ron Blaschke:
>> - After I changed the linkage, some dynclasses failed, during access
>> of C<Parrot_base_vtables[100]>. No surprise, as the array is only
>> C<#define PARROT_MAX_CLASSES 100>
>> long. After I changed it to 1000, the tests passed. Why gets no one
>> else bitten by this? Somehow my fault? Shouldn't it be dynamically
>> resized?
> Absolutely. I don't want to speak for Leo, but: "Patches welcome."
include/parrot/pmc.h:#define PARROT_MAX_CLASSES 100
include/parrot/pmc.h:VAR_SCOPE VTABLE **Parrot_base_vtables; \
/*[PARROT_MAX_CLASSES];*/
C<PARROT_MAX_CLASSES> defines the initial allocation size,
C<Parrot_base_vtables> should grow on demand. Maybe there's a bug in the
resizing code.
> On the one hand, IMCC doesn't really help you _run_ code, so I'm not
> inclined to see it part of libparrot. On the other hand, I haven't
> grokked the entire code base organization, so I could be Greatly
> Missing The Point.
Inside imcc/main.c is Parrot's main() entry. As soon as you load a
sourcecode file with C<load_bytecode>, the assemblers inside imcc are
needed to translate the source to PBC.
leo
