Bonjour Jean-Louis: just starting to look into your closure implementation.
It looks as if one is able to define any Rexx code as a literal by using curly brackets around them. These literals can then be run/executed later. Do you have a brief problem, example where one can see what is needed for a "bare-bone" closure and how it helps solve some problems in an easier way than with what is currently available in ooRexx? Or maybe reformulated: what is special about the closures, that makes it easier for the programmer to take advantage of them, rather than using what ooRexx has already? What do closures allow for, that is not really possible now? TIA, ---rony ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel