On Mon, Aug 25, 2008 at 2:39 PM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> This new "bug" request is probably more of an enhancement request than > a bug. This was not something it was possible (ok, easy) to fix in > the 3.x code base, but definitely is fixable in the 4.0 version. Taking this a little out of order. > I can go either way. The "easy" approach is working as designed. I'm > not sure this is the correct approach, however. I tend to agree that I'm not sure it is the correct approach either. But, I had thought that .local was not global. Is it just the way the interpreter is being started in the bug report? Well a quick test shows if I start an ooRexx program in one console window and then start another ooRexx program in another window, their .local environments are separate. Would this change under your proposal? > In this new scenario, .environment remains a global entity, shared > between all interpreter instances. Does this mean all interpreter instances in the same process space, or all interpreter instances running on the same system? -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
