Oh yeah...good point...:)
This patch has been applied.
Thanks!
-Original Message-
From: Will Coleda
To: Gibbs Tanton - tgibbs
Cc: '[EMAIL PROTECTED] '
Sent: 9/15/2001 12:33 PM
Subject: Re: Difficulties
Um... with the current setup, there IS no Makefile until you run
Configur
Um... with the current setup, there IS no Makefile until you run
Configure.pl, so I really don't see how that's possible. =-)
Gibbs Tanton - tgibbs wrote:
>
> The README really doesn't have to mention Configure.pl because when you do
> make test_prog it will run Configure.pl for you (at least it
I haven't had any problem with my instead of use vars...can you send me the
test program that blows up?
-Original Message-
From: Uri Guttman
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: 9/15/2001 8:57 AM
Subject: Re: Difficulties
>>>>> "
> "BD" == Brent Dax <[EMAIL PROTECTED]> writes:
BD> use vars qw(%opcode $fingerprint);#or strict will throw a tantrum
so why didn't 'my' work. those are file globals from what i can tell. my
causes interpreter.c to blow up. use vars fixes it.
uri
--
Uri Guttman - [EMA
> "WC" == Will Coleda <[EMAIL PROTECTED]> writes:
WC> The README doesn't mention Configure.pl (minor doc patch follows), and
WC> Parrot::Opcode is requiring perl5.6, which makes my 5.5.3 quite unhappy.
i noticed both of those problems.
i found Opcode.pm has a use 5.6.0 and it uses our.
Damien Neil:
# On Sat, Sep 15, 2001 at 01:52:26AM -0700, Brent Dax wrote:
# > use vars qw(%opcode $fingerprint); #or strict will throw a tantrum
#
# Not necessary--the patch changes those variables to lexicals.
# There wasn't any strong reason for them to be package vars.
Oh, duh... *smacks his
On Sat, Sep 15, 2001 at 01:52:26AM -0700, Brent Dax wrote:
> use vars qw(%opcode $fingerprint);#or strict will throw a tantrum
Not necessary--the patch changes those variables to lexicals.
There wasn't any strong reason for them to be package vars.
- Damien
Damien Neil:
# On Sat, Sep 15, 2001 at 01:15:57AM -0700, Brent Dax wrote:
# > As for the 5.6 thing...I think we're supposed to support 5.005 and
# > above. Can you tell what Parrot::Opcode needs it for?
# (And if it's for
# > 'our', I'm going to punch someone... :^) )
#
# Er...I think it IS fo
The README really doesn't have to mention Configure.pl because when you do
make test_prog it will run Configure.pl for you (at least it is supposed to
:)
-Original Message-
From: Will Coleda
To: [EMAIL PROTECTED]
Sent: 9/15/2001 12:13 AM
Subject: Difficulties
The README doesn't mention
Will Coleda wrote:
>
> The README doesn't mention Configure.pl (minor doc patch follows), and
> Parrot::Opcode is requiring perl5.6, which makes my 5.5.3 quite unhappy.
>
> Are folks intentially using 5.6 constructs? I'll consider generating a
> patch to make things work with 5.5.3 if this was
10 matches
Mail list logo