On Thu, Aug 03, 2006 at 12:05:13PM -0700, chromatic wrote:
> On Thursday 03 August 2006 11:18, Chip Salzenberg wrote:
> > The whole question of packfiles is something I hadn't approached before,
> > and now that I have, I wonder: Why does a packfile needs to exist at all
> > when compiling into the
On Aug 3, 2006, at 2:05 PM, chromatic wrote:
PS: Cage cleaners should detect and possibly correct all that
namespace
pollution. Yuck.
In the external API, you mean? Isn't there a bug for creating
macros to avoid
prefixing Parrot_ to all internal-only functions?
That is one of my first
On Thursday 03 August 2006 11:18, Chip Salzenberg wrote:
> The whole question of packfiles is something I hadn't approached before,
> and now that I have, I wonder: Why does a packfile needs to exist at all
> when compiling into the in-memory interpreter? There are some answers to
> that question
The whole question of packfiles is something I hadn't approached before, and
now that I have, I wonder: Why does a packfile needs to exist at all when
compiling into the in-memory interpreter? There are some answers to that
question I'd accept, but it's still a question that needs answering.
As f
On Friday 28 July 2006 10:23, Leopold Toetsch via RT wrote:
> Am Freitag, 28. Juli 2006 18:41 schrieb chromatic:
> > Hm, sort of. Is there any reason not to call it from Parrot_new() and
> > not make the C API users do it?
>
> Well, when the next (and maybe common) step is:
>
> pf = Parrot_rea
Am Freitag, 28. Juli 2006 18:41 schrieb chromatic:
> Hm, sort of. Is there any reason not to call it from Parrot_new() and not
> make the C API users do it?
Well, when the next (and maybe common) step is:
pf = Parrot_readbc(interp, sourcefile);
then the creation of the dummy PF structure was
On Friday 28 July 2006 07:26, Guest via RT wrote:
> This should be fixed now with r13613.
Hm, sort of. Is there any reason not to call it from Parrot_new() and not
make the C API users do it? I don't really want to require them to
understand the use of packfiles or pull in parrot/packfile.h e
# New Ticket Created by chromatic
# Please include the string: [perl #39986]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39986 >
Hi there,
When creating a new interpreter with Parrot_new(), it should be possible to
com
