On Thu Nov 08 12:23:50 2007, kjs wrote:
> To my knowledge, the :init flag is implemented and there are no problems
> with it.
>
> Is there any reason not to close this ticket?
>
> kjs
forgot to cc the list. See my previous comment.
kjs
Klaas-Jan Stol via RT wrote:
Is there any reason not to close this ticket?
Do it.
Allison
Am Mittwoch, 18. Oktober 2006 20:46 schrieben Sie:
> Do you thing you could annotate the rest of the flags as to when they
> are used?
typedef enum {
SUB_FLAG_CORO_FF = PObj_private0_FLAG, /* r */
SUB_FLAG_C_HANDLER= PObj_private0_FLAG, r / C exceptions only
SUB_
Thanks I didn't know which flag too pick.
I finally did get flex and bison to run.
Do you thing you could annotate the rest of the flags as to when they
are used?
Kevin
Leopold Toetsch wrote:
Am Mittwoch, 18. Oktober 2006 17:20 schrieb Kevin Tew:
Working code with test.
I stole PBC_POS
Am Mittwoch, 18. Oktober 2006 17:20 schrieb Kevin Tew:
> Working code with test.
>
> I stole PBC_POSTCOMP's flag for the short term.
That's an unfortunate decision. There are load-time flags and run-time flags.
You can just take one of the runtime-flags. I'd propose you use:
SUB_FLAG_TAILCAL
The issue of having an :init pragma for subs came up again during
today's #parrotsketch meeting, and I volunteered to summarize the
discussion for ticket #39926 and the mailing list.
The :init pragma is intended to make it easier for automatically
generated modules to make sure that initialization
