jerry gay wrote:
On 12/22/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Tuesday, December 20, 2005, 8:09:32 PM, François PERRAD wrote:
At 11:53 16/12/2005 +0100, you wrote:
I can think of two ways to fix this:
- Hide every env access behind the platform stuff. That is, add
something like Parro
On 12/22/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Tuesday, December 20, 2005, 8:09:32 PM, François PERRAD wrote:
> > At 11:53 16/12/2005 +0100, you wrote:
>
> >>I can think of two ways to fix this:
> >>
> >>- Hide every env access behind the platform stuff. That is, add
> >>something like Par
Tuesday, December 20, 2005, 8:09:32 PM, François PERRAD wrote:
> At 11:53 16/12/2005 +0100, you wrote:
>>I can think of two ways to fix this:
>>
>>- Hide every env access behind the platform stuff. That is, add
>>something like Parrot_environ.
> For me, this way sounds better.
> The platform/env
Lacking committer privileges, I'd like to discuss patches first. I'll
only start coding anything after I received at least one +1 from a
committer. After that I would submit a patch and wait for it to be
applied or rejected. That way I hope to avoid warnocked patches.
t/pmc/env.t is failing on
