On Sun, May 16, 2010 at 02:55:36AM -0500, Tyler Curtis wrote: > Currently, there are low-level PMC interfaces(is there a name for > them) that PMCs can provide for "array"s, "boolean"s, "event"s, > "float"s, "Handle"s, "integer"s, "library"s, "scalar"s, "socket"s, and > "string"s. There is no "sub" low-level interface for PMCs that support > being invoked, even though there are 11 different core PMCs that have > custom invoke methods. I suppose no one has needed one so far. I'll > soon be implementing PAST traversal[0] and pattern matching[1] > libraries for use in writing optimizations. Something that would be > very useful in PAST::Pattern would be a way to detect that a PMC can > be invoked. A "sub" low-level interface for PMCs that can be invoked > would greatly simplify some aspects of its implementation. > > Should we add such an interface? Is there any reason not to?
I also need this for blizkost (which generates proxies in P5-land depending on supported Parrot roles). http://trac.parrot.org/parrot/ticket/1597 -sorear
signature.asc
Description: Digital signature
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
