Re: IL Engineering Library
- Posted by jimcbrown (admin) Jul 20, 2015
- 3140 views
Sorry to quote from a very old (2004) post [1].
You still won't be able to create new routines at runtime and have them execute in the same address space as the application (eg. have them share variables). With using routine-id, you can only deal with routines that already exist at runtime. There is a convoluted method of doing this in WIndows/Linux environments, but it involves compiling a new routine as a shared library (eg. a Windows DLL) at runtime then loading that library, then running the routine - not a pretty method at all.
@Jim: I was wondering, how was your IL Engineering Library able to overcome the limitations mentioned by Derek?
Actually, your quote shows that Derek already knew of a way of overcoming those limitations.
Meanwhile, my example implementation does not support creating new routines at runtime yet. This would require hooking into the routine_id table and stuff, which can be done, but simply has not been implemented yet.
And are the new routines created at runtime actually sharing the same address space as the rest of the program?
Yes.
