[Oorexx-devel] Questions ad extension-mechanism ... (Re: Ad experimental ooRexx ... (Re: Question ad rev. 7391 (sandbox/jlf)
Bonjour Jean-Louis, experimenting with your (great and colorized!) oorexxshell-replacement for rexxtry.rex, I saw that you have been applying your new extension mechanism in some of the Rexx pakcages that you automatically load, e.g. extension/extension.cls. A few questions: * How stable is your implementation of extensions? Are there any unexpected side-effects to be expected? * How can one achieve the following extension (from extensions.cls) directives dynamically at runtime (e.g. if one creates a method object for the 'quoted' method at runtime, how could one use that to extend the .String class at runtime) ? ::extension String ::method quoted use strict arg quote='' return quote || self~changeStr(quote,quote||quote) || quote * How is it possible to learn which methods got extended in a class? * What happens, if different programs extend a class with a method by the same name? Is this allowed, and if so what are the rules (each extension method replaces an exisiting extended method; or it is an error to extend a method, if the method exists already)? * Is it possible to remove an extended method later in the program? If so, how? For sure your extension mechanism would solve quite a few problems for ooRexx programmers, who have a need to extend existing classes for their purposes. I remember there were from time to time requests to allow for that, especially extending some of the Rexx-supplied classes, e.g. the .String class, which seems to work judging from your ooRexxShell employed extensions.cls! Very interesting, indeed ! Best regards, ---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
[Oorexx-devel] Question at .CoRoutine ... (Re: Ad experimental ooRexx ... (Re: Question ad rev. 7391 (sandbox/jlf)
Bonjour Jean-Louis, maybe a stupid question: what is the purpose of a .CoRoutine? How does that differ from having Rexx methods execute concurrently? What does one need to know to decide whether to use a CoRoutine or not? 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
[Oorexx-devel] Question ad closures... (Re: Ad experimental ooRexx ... (Re: Question ad rev. 7391 (sandbox/jlf)
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
