Mark, In your last commit for your winshell 4.0 rework, something caught my eye. I noticed that code is still stuffing class entries into .local. That's the same sort of hack that oodialog was doing (but done differently, of course :-)). Things that use the winshell classes really should be doing a ::requires on the package file rather than relying on something else having done it for them. I think maybe that code should be deleted, and if there is a chorus of loud screams about stuff no longer working, it can always get added back in.
The other possibility would be to revise the "globally public" concept I raised earlier. Now that the package manager stuff is done, this would be a fairly trivial thing to add to allow packages to declare something to be in a global context once the package has been loaded the first time. We can start with just removing that, and if compatibility is an issue, then we can implement the more general solution rather than restore the hack. Rick ------------------------------------------------------------------------- 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
