Re: import() functions from another module

I second that, but I thought regex != m// was an important point. If M is uncertain about where regexes can be used, I'm happy to help him out ;) cool :) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: import() functions from another module

On 4/14/05, JupiterHost.Net <[EMAIL PROTECTED]> wrote: > >>Jay Savage wrote: > >>[snip] > >> > >>>But think a little bit about the convoluted namespace you created to > >>>get that function in there. Think also about this: why have you put > >>>this code into a module? So you can reuse it, presu

Re: import() functions from another module

Jay Savage wrote: [snip] But think a little bit about the convoluted namespace you created to get that function in there. Think also about this: why have you put this code into a module? So you can reuse it, presumably. Or at least that's the assumption I'm working with. Maybe you're even goin

Re: import() functions from another module

On 4/14/05, M. Kristall <[EMAIL PROTECTED]> wrote: > Jay Savage wrote: > [snip] > > But think a little bit about the convoluted namespace you created to > > get that function in there. Think also about this: why have you put > > this code into a module? So you can reuse it, presumably. Or at >

Re: import() functions from another module

Jay Savage wrote: [snip] But think a little bit about the convoluted namespace you created to get that function in there. Think also about this: why have you put this code into a module? So you can reuse it, presumably. Or at least that's the assumption I'm working with. Maybe you're even goin

Re: import() functions from another module

[snip] Digest::MD5, and tomorrow, I decide that the function isn't going to be called 'md5_base64' anymore, because I got sick of typing it. From now on it's going to be 'md5_64'. You now have to go through and fix your module to make it export the new function name. That is exactly the point o

Re: import() functions from another module

On Apr 1, 2005 4:04 PM, JupiterHost.Net <[EMAIL PROTECTED]> wrote: > > Are you even serious? I sent the exact code that reproduced the problem. > You said you didn't have time to run it which is fine, > but it was there :) > The code you sent 1) was oversimplified and 2) presented you as creati

Re: import() functions from another module

Thanks for your input, I beleive I may have not been clear aboutthe goal and apologize if it confused you. Lee, It's generally best to provide as real-world an example as possible when asking for help on this list. Code doesn't confuse things--or people--around here. We all look at the code you s

Re: import() functions from another module

On Apr 1, 2005 12:03 AM, JupiterHost.Net <[EMAIL PROTECTED]> wrote: > > Assuming that your import() does what you think it does--and I don't > > have time to test it, but as long as you're USEing it anyway, why not > > just write a wrapper instead of the pass-the-import nonsense--you > > Because t

Re: import() functions from another module

Joshua Colson wrote: On Thu, 2005-03-31 at 12:41 -0600, JupiterHost.Net wrote: Hello, I am working on a module that needs to import a function from Digest::MD5. The reasoning on this is that its a subclass so it'd be handy to be able to use() it and export functions from the parent module witho

Re: import() functions from another module

Any ideas would be most appreciated! I think all you need to do is export the md5_base64 sub from FooTest That and add Diget::MD5 to @ISA :) Now it works great! Thanks to all who helped with this! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: import() functions from another module

Assuming that your import() does what you think it does--and I don't have time to test it, but as long as you're USEing it anyway, why not just write a wrapper instead of the pass-the-import nonsense--you Because then I have to add and manage a wrapper for each new function and keep up with the pa

Re: import() functions from another module

On Thu, 2005-03-31 at 12:41 -0600, JupiterHost.Net wrote: > Hello, > > I am working on a module that needs to import a function from > Digest::MD5. The reasoning on this is that its a subclass so it'd be > handy to be able to use() it and export functions from the parent module > without having