On Wed, Jan 16, 2002 at 11:39:05AM +0100, Mattia Barbon wrote:
> >It seems that's wrong. That what perlcc/B::C does is 'freeze' the
> >current state of the interpreter after compilation, including the
> >values of variables, and then spit out appropriate C code for only
> >the post-compile opcod
On Tue, Jan 15, 2002 at 05:30:09PM -0500, [EMAIL PROTECTED] wrote:
> On Tue, Jan 15, 2002 at 08:51:06AM +, Piers Cawley wrote:
> > > I don't understand. Why do we have to deal with them? Just translate
> > > the Perl code in the BEGIN block to C , dump it and make
> > > sure it gets run firs
On Wed, 16 Jan 2002, Michael G Schwern wrote:
>On Wed, Jan 16, 2002 at 08:45:26AM +0100, Paul Johnson wrote:
>> The fundamental problem here is that BEGIN blocks have to run when they
>> are compiled. This is documented. You can try to work out whether the
>> BEGIN blocks can be rearranged and
On Wed, Jan 16, 2002 at 08:45:26AM +0100, Paul Johnson wrote:
> The fundamental problem here is that BEGIN blocks have to run when they
> are compiled. This is documented. You can try to work out whether the
> BEGIN blocks can be rearranged and run at different times, but as Piers
> has pointed
