At 7:42 PM +0200 4/19/02, Marco Baringer wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
>
>> Ah, this is incorrect. goto ADDRESS should go to an absolute address,
>> period. It's for use in those times when you *have* an absolute
>> address--for example w
On Thu, Apr 18, 2002 at 11:11:31PM +0200, Marco Baringer wrote:
> Jason Gloudon <[EMAIL PROTECTED]> writes:
>
> > So thus far, goto ADDRESS(X) means set the program counter to the pointer value
> > X.
>
> ok, but i find this highly counter-intuitive.
I used to
Dan Sugalski <[EMAIL PROTECTED]> writes:
> Ah, this is incorrect. goto ADDRESS should go to an absolute address,
> period. It's for use in those times when you *have* an absolute
> address--for example when you've just fetched the address of a
> subroutine from a s
At 11:11 PM +0200 4/18/02, Marco Baringer wrote:
>
>i am attaching a patch to Parrot::OpTrans::CGoto which makes goto
>ADDRESS(X) jump to the offset X relative to the start of the byte_code
>(in other words interpreter->code->byte_code + X). given this "new"
>int
>
> > in trying to make goto ADDRESS($1) work as it should i have come
> > across the following doubt:
>
> How are you interpreting that it "should" work ? I don't know of any
> documentation that says what it should do, but currently it is only used to
&
On Thu, Apr 18, 2002 at 01:49:20PM +0200, Marco Baringer wrote:
> in trying to make goto ADDRESS($1) work as it should i have come
> across the following doubt:
How are you interpreting that it "should" work ? I don't know of any
documentation that says what it should do
in trying to make goto ADDRESS($1) work as it should i have come
across the following doubt:
out of core_ops.c, core_ops_cg.c and core_ops_prederef.c which one is
parrot using? and how do i change it if i want? i notice while
compling is have the HAVE_COMPUTED_GOTO macro defined, but it seems
