Re: Tiny imcc example doesn't work

[gregor]

Thanks for the tip.

I think I can use that to work around the limitation. It makes it 
unnatural to
have a script with the pattern:

     some code
     some subroutine definitions
     some more code, calling the subroutines.

Which Jako permits.

It looks like I can wrap all the bits of miscellaneous code in little 
pseudo-
subs:

    .sub __CODE__0
        ...
        goto __CODE__1
    .end

    .sub some_real_sub
       ....
    .end

    .sub __CODE__1
       ...
       call some_real_sub
       ...
    .end

And just ignore the spurrious 'ret' instructions imcc generates to 
"properly"
terminate each of the "subroutines" (if imcc ever does dead code removal,
it could actually remove these instructions before they make it to the 
..pasm
file).


Regards,

-- Gregor





"Mr. Nobody" <[EMAIL PROTECTED]>
12/04/2002 10:15 AM

 
        To:     [EMAIL PROTECTED]
        cc:     [EMAIL PROTECTED]
        Subject:        Re: Tiny imcc example doesn't work



--- [EMAIL PROTECTED] wrote:
> I thought that something like what follows:
> 
>     goto _foo
>     end
>     _foo:
>     print "Howdy!\n"
>     end
> 
> would be legal imcc input

IMCC requires you to put everything in .subs. So it should be something 
like

..sub main
goto _foo
end
_foo:
print "Howdy!\n"
end
..end

There's nothing special about calling it "main", the pasm entry point is 
the
first sub.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com