Hmm. You know what I just found out? The ParrotInterpreter PMC doesn't implement set_pmc_keyed. Any objections to implementing it? It could then be expanded to support getting and setting interpreter flags, which are currently handled through get_ and set_integer_keyed_int. Providing a keyed string interface to the flags would be a lot nicer than OR-ing values together.
Come to think of it, why are we using a keyed interface at all? Why can't we just use getprop and setprop, or getattribute and setattribute? It's what they were designed for, after all. On 3/30/07, Alek Storm <[EMAIL PROTECTED]> wrote:
How about like this: $P0 = getinterp $P0["recursionlimit"] = 2000 $P0["recursionlimit"] = -1 Where the last one signifies an infinite recursion limit (unsafe, but it should still be available to HLL implementors). On 3/30/07, chromatic <[EMAIL PROTECTED]> wrote: > On Friday 30 March 2007 13:38, Paul Cochrane via RT wrote: > > > Thanks! Applied in r17863. > > It would be pretty simple to make this a settable/queryable interpreter > property. Would that be valuable? > > -- c >
