Hi Jean-Louis, thank you very much for looking into this so thoroughly, which allows me to understand what is going on and why you think this is not possible.
On 02.06.2011 18:46, Jean-Louis Faucher wrote: > I don't think it's possible to do a native reply, see code review below. > Maybe if you split your native method in two separate native methods > then you could use reply like that ? > > ::class ConcurrentNatives > ::method native1 EXTERNAL "LIBRARY mylibray native1" > ::method native2 EXTERNAL "LIBRARY mylibray native2" > ::method createThread > self~native1 > reply > self~native2 > > I don't know if there are restrictions about the way createThread is > called... > i.e. can a reply be executed from a rexx method called from user C++ > code ? Well, will see and report back (will take some time before I will be able to get there due to my current work-load; but steadily things move on step by step...). > Code review... > The reply instruction just sets a flag in the current RexxActivation, > and force the end of the current interpreter loop by saying "no more > instruction". > Then the interpreter sees the reply flag and creates a new RexxActivity. > > In the attached file, I kept only the lines interesting for our > understanding of the reply. > Three methods to read, make your own opinion :-) Thank you *very* much for this interesting analysis! Best regards, ---rony ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
