On Sun, Apr 6, 2008 at 10:30 AM, Bob Rogers
<[EMAIL PROTECTED]> wrote:
>From: Bob Rogers <[EMAIL PROTECTED]>
>Date: Sun, 6 Apr 2008 13:25:33 -0400
>
>
>
> From: chromatic <[EMAIL PROTECTED]>
> Date: Sun, 6 Apr 2008 09:52:34 -0700
>
> ... compounded by the fact that I can't
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 6 Apr 2008 13:25:33 -0400
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 6 Apr 2008 09:52:34 -0700
... compounded by the fact that I can't seem to get any of the existing
namespace ops to do what I want in a concise, n
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 6 Apr 2008 09:52:34 -0700
... compounded by the fact that I can't seem to get any of the existing
namespace ops to do what I want in a concise, non-hacky way. What am I
missing?
I notice that changing "get_root_namespace" to "get_hl
On Sunday 06 April 2008 09:33:06 chromatic wrote:
> On Sunday 06 April 2008 02:17:07 Jonathan Worthington wrote:
> > The behavior looks sane to me. .include is, quite literally, textual
> > inclusion, nothing more. The get_namespace instruction is always
> > relative. The code should probably be
On Sunday 06 April 2008 02:17:07 Jonathan Worthington wrote:
> The behavior looks sane to me. .include is, quite literally, textual
> inclusion, nothing more. The get_namespace instruction is always
> relative. The code should probably be using an absolute namespace op,
> such as get_hll_namespace
chromatic wrote:
Based on my reading of the documentation for get_namespace, this behavior
isn't surprising, but based on what I want to do with the code, this behavior
is very surprising:
works.pir:
.sub 'main' :main
.include 'runtime/parrot/include/test_more.pir'
Based on my reading of the documentation for get_namespace, this behavior
isn't surprising, but based on what I want to do with the code, this behavior
is very surprising:
works.pir:
.sub 'main' :main
.include 'runtime/parrot/include/test_more.pir'
.end
breaks.p
