Generally, it would be good to open an RFE for the specific item you wish to implement. It would be fine to include the function of having a threadlocal as part of that RFE and close both once they are implemented.
For something of this scope, I think you need to write the documentation (or at least a skeleton of the docs) for the feature so people can see what you're really adding. Rick On Sat, Mar 5, 2011 at 4:01 PM, Jean-Louis Faucher <jfaucher...@gmail.com> wrote: > > > 2011/3/5 Rick McGuire <object.r...@gmail.com> >> >> Ok, I'm definitely -1 on adding this then. First of all, you're only >> adding this for Unix systems, but working on adding a facility that is >> generally useful. This is exactly the sort of usage I'm against. >> >> A better approach would be to define an ooRexx thread object that >> provides different facilities, including the ability to have named >> values associated with the thread. This is something that could >> easily be returned by the .Context object. >> > Sounds good. > But then, how to proceed ? > Can't find on the dev list a procedure that is followed when a change is > proposed (or I miss it...). Should the proposed change be documented in a > RFE ? > If yes, can RFE 2868655 be used for this work ? The initial proposition > (.threadLocal) is not like yours (ooRexx thread object), so I don't know... > > Regards > Jean-Louis > > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
