"Require" works on the top level package but the thing is so nested I will end up with errors at the next level.
I just needed a quick temporary work around. In this thread, I discovered a third option that works for me. Problem definition How to make easy use of some private subs in a package when the package requires many dependencies. Workarounds 1. install all dependencies 2. copy and paste subs inline 3. use fully qualified package name Option 3 works best but I have to comment out some code that I do not need in the package and its dependencies. This is not a problem because these changes are temporary. Doing so allows me to write my script in the exact syntax needed with less hassles than Options 1 and 2. I will definitely rollback the packages once I am done. I like it. Thank you. On Sun, 14 Jul 2002 18:10:56 +0100, [EMAIL PROTECTED] (Daniel Gardner) wrote: >Does doing a require work, so that the import isn't called? > >If it's just the import that causes the failure you should >be able to require and then use whatever subroutines are in >there by fully qualifying the package name. > >HTH, >Daniel > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
