On Thu, Sep 04, 2008 at 12:25:36PM -0500, Patrick R. Michaud wrote: > On Thu, Sep 04, 2008 at 09:48:09AM -0700, chromatic via RT wrote: > > > I don't think we need any specialized opcodes for this -- simply > > > being able to introspect and dynamically modify the current > > > interpreter's HLL mapping tables ought to be sufficient. > > > > > > (Introspection of HLL mappings is likely to end up being important > > > for the compiler toolkit related libraries anyway, so that a toolkit > > > can generate correct mapping code in the places where Parrot doesn't > > > already handle it.) > > > > How would the interface look? Are methods on the > > Interpreter PMC appropriate, or do you have something else in mind? > > I don't have a specific interface in mind. Methods on an > Interpreter PMC would be just fine, and are probably preferable: > [...]
I should also note that for what I'm looking at now, being able to set hll type mapping is the important feature that could be used relatively soon, while introspection of type mapping is something that we'll eventually want but isn't needed as urgently. Pm
