On Sun, Jun 29, 2008 at 9:30 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> The more I looked at it, the more I realized that all of that logic > was just a mechanism to get around the fact that the old ::REQUIRES > mechanism was reloading the referenced source file in each program > that had a ::REQUIRES for the named file. The OODIALOG classes used > another hack to force the OODIALOG *.cls files from getting loaded > more than once, but that hack also required that all of the classes > and routines be essentially made global. Yes, it definitely was logic to get around loading a required file over and over. I did similar things in code I wrote some years ago. > I scrapped that entire mechanism and replaced it with the new > PackageManager, which allows all programs in the interpreter to share > a single instance of a referenced ::requires file. As long as all of > the programs indicate they required the file, they'll pick up access > to the included classes and routines. The PackageManager only reading and parsing a required file one time, will eliminate most of my reasons for not wanting to have a requires statement in every program file that is run in the same process space. Will this eliminate classes not comparing as equal when they are from different program files where both program files required the same class definition file? (Not sure if that articulates what I mean, hopefully you'll understand.) -- Mark Miesfeld ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
