[EMAIL PROTECTED] wrote:
A quick glance in the "Implementation of the Icon Programming Language" revealed that Icon bytecode is rather high-level and the translation step is not that complicated. The .Net bytecode, being lower-level, would require partial inclusion of the icode interpreter itself in the Icon (or its ucode) to .Net bytecode translator.
It's been a *long* time, so perhaps my memory is warped, but I thought that Icon's goal-directed-evaluation model was implemented below the icode level (that is, there's the moral equivalent of a "suspend" icode command). If that's true, then is the translation of icode to .Net bytecode truly "not that complicated"? Certainly it can be done or the JVM version of Icon wouldn't exist, but it may take some thought (or blatant stealing from the iconj work...). Co-expressions *may* also introduce some complexity.
-Steve
-- Steve Wampler -- [EMAIL PROTECTED] The gods that smiled on your birth are now laughing out loud.
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
