On 9/5/2010 4:51 PM, P Kishor wrote: > On Sun, Sep 5, 2010 at 1:39 PM, Chris Marshall<[email protected]> wrote: >> On 9/5/2010 2:20 PM, P Kishor wrote: >>> a few of PDL's multitude of commands are conflicting with the commands >>> of another framework (Perl Dancer). I have asked the developers of >>> Dancer this question, and in the meantime, I ask PDL developers also >>> -- is it possible to "de-export" any or all PDL commands. For example, >>> I would like to be able to call 'any' as 'PDL::any' but not 'any'. Is >>> that possible? >> >> Try 'help PDL' in the shell or 'perldoc PDL' >> > > > Hi Chris, I know you want to lead me to the answer, but I am not sure > where you are pointing me to. I have looked at "help PDL" and "perldoc > PDL" and the only item of relevance to me here I see is > > "Exports > use PDL; exports a large number of routines into the calling > namespace. If you want to avoid namespace pollution, you must instead > use PDL::Lite, and include any additional modules explicitly."
If you want to avoid namespace pollution, you must instead use PDL::Lite, and include any additional modules explicitly. > So, how does that help me? If I use PDL::Core, I get 'set', and then, > PDL's 'set' redefines another package's 'set'. > > Same thing with 'any'. If I use PDL::Ufunc, I get PDL's 'any' which > then redefined a different 'any'. > > My question -- can I 'use PDL' but not import its methods? Or better > yet, import selectively? Or, even better, prefix all of PDL's methods > with 'PDL::' no matter in which PDL module they reside? _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
