> -----Original Message----- > From: Yuriy Zhilovets [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 07, 2005 5:33 AM > To: unicon-group@lists.sourceforge.net > Subject: [Unicon-group] Separate icode files > > > Hi, everybody > > Is any way to produce a separate icode file? > It seems that overhead of 600 kilobytes of binary code for a > single program > in 100 bytes of icode is a bit of overhead? > > Yuriy Zhilovets
I was having the same problem and asked the same question on 11/19/2003. Clint Jeffery said: > Last I checked, if you specify that an output icode file > should end with the > extension .cmd (and possibly also .bat), Unicon will write > out icode without > iconx prepended to it. You can then invoke iconx explicitly, > passing it the > icode file as its first argument, as in the good old days. I tried it and it worked. My reply was: > Sure did. (My program is named "include.icn".) > "icont -o include.cmd include" > built an include.cmd of a mere 1728 bytes. > "iconx include.cmd include.txt" > (include.txt is my test input) ran it like a champ. Works for me! I also made this remark: > It might be good to update your basic documentation to point out > the .cmd trick, though. I couldn't find that anywhere. I stand by it. Charlie Hethcoat ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Unicon-group mailing list Unicon-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unicon-group
