goer@ellis.uchicago.edu (Richard L. Goerwitz) (12/21/90)
Rather than mail out individual copies of my Icon termlib-like routines, I decided to post them to alt.sources. People who don't get alt.sources, write me. I will send out individual copies to those who request them. I've burdened this non-source group with a lot of source code already, and I believe it will be much bet- ter to put this rather largish posting in a more appropriate place. This is a repost, but I believe it is justified by the improvements I've made, and also by the simple fact that I was asked to post them again. -Richard (goer@sophist.uchicago.edu)
beser@tron.UUCP (Eric Beser) (01/03/91)
Given the ability to call c routines from icon, and for c routines to call icon, has anyone done an Xwindows interface for icon? If not, I volunteer (ugh). In order to do this, I need the following information. I looked for Griswald's book on implementation of icon, and no one has it. Anywhere. What I need is a better discription than what the tech reference that came with rev 8 has (which refers to Griswald's book). I have written interpretive interfaces before, and I have a rough idea how it may work, but I would appreciate someone sending me any information on icon calling conventions and function return conventions. Or at least where to look. Handling callbacks from X would be done through C interfaces to ICON. The callbacks would be registered through the runtime and would return through the runtime. My confusion is about how the status information, or pointers to X structures would be passed back to ICON. Anyone willing to help, kindly let me know through email. Eric Beser Westinghouse Aerospace Software Engineering beser@tron.bwi.wec.com