Greetings to all. I've been lurking awhile on this list. Now I have a question.
The people in my workgroup all use Windows. Some also use Cygwin, but not all. Some are programmers, but not all. I'll bet money none of them knows Icon, let alone Unicon! I'd like to write some little but useful programs for these folks, and I'd like to use Unicon to do it. I would prefer to distribute an executable form of each program, and not have to mess with source code on the user's machines. A logistical question arises. The default behavior for Windows Unicon is to compile to a self-executing file. If I understand correctly, each of these files includes its own complete copy of iconx. That's convenient, but the files are huge. As an example, a little Icon utility program of only 21 nonblank lines, when compiled, swelled into 553 KB! So, if I write a couple of dozen similar programs and distribute them to everyone in my group, we are talking some serious bloat. I think I would prefer to go back to the old-style icode object files, and separately install the runtime interpreter, iconx, on people's machines. This will only hurt once, and each new program, in icode, is almost free. So my question is, can I turn this behavior back on with the Windows version? Any other suggestions? Thanks. Charles Hethcoat ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
