On Tue, Sep 22, 2009 at 4:13 PM, Rick McGuire <[email protected]> wrote:
> Unfortunately, you're going to run into scoping problems with this > approach. The merged file will work ok, but the smaller stub files > won't be able to make the public classes from the merged file public > by just having a ::requires for the merged package. I did a quick test and it seemed to work. I must be missing some basic point you are making here. (Not surprising, scoping often trips me up. <grin>) Right now if you ::require oodWin32.cls, it has a ::require 'ooDialog.cls' which has a ::require 'oodPlain.cls' The public classes in oodPlain.cls are public in your program when you require oodWin32.cls. I not sure I see why moving all the classes in oodWin32.cls into, say oodPlain.cls, would change anything there? All the public classes in oodPlain.cls would still be public in your program that required oodWin32.cls. -- Mark Miesfeld ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
