On Thursday 04 September 2008 08:44:26 Patrick R. Michaud (via RT) wrote: > Currently the only (documented) way to set up HLL mapping is > by using the .HLL_map directive in PIR. However, this leads > to a bootstrapping problem of sorts when attempting to > map classes created in PIR (which often aren't created until > load/init time). > > 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? -- c
