Re: Invoking a function using full package name fail, but works without full package name
- To: mathgroup at smc.vnet.net
- Subject: [mg52586] Re: Invoking a function using full package name fail, but works without full package name
- From: "Jens-Peer Kuska" <kuska at informatik.uni-leipzig.de>
- Date: Fri, 3 Dec 2004 03:53:46 -0500 (EST)
- Organization: Uni Leipzig
- References: <comg11$5ps$1@smc.vnet.net>
- Sender: owner-wri-mathgroup at wolfram.com
Hi, it is so, because the ImageProcessing calls an other package for the data import and ImageRead[] is implemented in the ImageProcessing`ImageData` package and it stand in this context. So if you "to know where each function is comming from" you have to *know* where thie function come from. Regards Jens "nospam nospam" <nospam_please at nospam.com> schrieb im Newsbeitrag news:comg11$5ps$1 at smc.vnet.net... > Hello; > > In my code, I usually like to add the package name to the > function name to know where each function is comming from. > (A sort of self documenting the code) > > Now I found this to cause a problem with this Mathematica > package. > > This is an example > > << ImageProcessing` > img = ImageProcessing`ImageRead["test.gif"]; > Show[Graphics[img]]; > > The above gives an error > > Graphics::gprim: ImageProcessing`ImageRead[test.gif] was encountered \ > where a Graphics primitive or directive was expected > > BUT when I do this: > > img = ImageRead["test.gif"]; > Show[Graphics[img]]; > > Then it works. > > This completely destroyes my naming convention of using full > package names in my code. > > any idea why this is so? It seems to work ok with another user > package I tried, but not this one?? > > thanks, > --nospam > > >