Re: load user defined module
- Posted by Igor Kachan <kinz at peterlink.ru> Nov 09, 2002
- 415 views
Hello Robert, ---------- > Îò: Robert Craig <rds at RapidEuphoria.com> > Êîìó: EUforum <EUforum at topica.com> > Òåìà: Re: load user defined module > Äàòà: 9 íîÿáðÿ 2002 ã. 5:50 > > Derek Parnell writes: > > Robert, > > is this the sort of thing you are suggesting for us ? ... > > ... > > ... > > As you could imagine, it would not take much for this to > > become very hard to maintain. Can you suggest a better approach? > > I don't know. There are various approaches that > you could take. > Igor's dynamic include approach is one, although > it won't work with the binder or translator. It works with binder and translator for me Just delete old con_libs.e from the current directory then run code with ex.exe interpreter. You'll have new con_libs.e for the DOS platform in the current directory. Then run bind code. You'll have .exe for DOS with that new con_libs.e included. bind.bat must run ex.exe, not exw.exe. Then run ec with code, then run emake.bat and you'll have compiled .exe for DOS. Then delete con_libs.e for DOS from the current directory and run code with exw.exe interpreter. You'll have new con_libs.e for the WIN platform in the current directory. Then run bindw code. You'll have .exe for WIN with that new con_libs.e included. bindw.bat must run exw.exe as it runs. Then run ecw with code, then run emake.bat and you'll have compiled .exe for WIN. So, the trick is to DELETE the bad con_libs.e and CREATE new good one with needed interpreter before binding or translation for the needed platform. <snip> Regards, Igor Kachan kinz at peterlink.ru