Re: Dynamic calling
- Posted by useless Sep 19, 2009
- 1301 views
So i can keep on not ever using routine_id with allocated memory, and it will now magically work? How does that work?!
I have already answered this:
(On the other hand, if this never worked in 3.1.1, DEP won't help you one iota in making this work in 4.0)
And i said i never DID that, so i don't know if it would have ever WORKED, and i don't know HOW to do it in v3.1.1 or v4, so i asked for DIRECTIONS. So when you say to keep doing that like i did, "like i did" = "not doing it at all", which makes "it works like it always did" be illogical. I stored the occasional DATA in memory, but never ever tried to execute the data there, because it wasn't machine code.
Ok, talked to Derek on irc, it was enlightening, and sad. No way at all to make eu code into something that the interpreter will be happy executing in a routine_id call to allocate() or allocate_code(). Unless, and this is just me thinking, er, on the keybd, of a stub of machine code at the routine_id, instead of the actual code i wish to run. The stub makes the routine_id look normal, and handles the code of a bound eu code i want to run in a hidden manner. I know it won't work, Derek told me already. But i did think of it.
useless
