Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
How do I get IDL to see that my procedure exists?
I'm a relative newbie at IDL so please bear with me... I wrote an IDL procedure to do what I want. I put it in a directory called /usr/users/Bowler/idl and called it anyData.pro. The first line of the file is PRO anyData, file, inbounds and it ends with an END. When I open the file in IDLDE and call it, it works fine. Now I want to do from the IDL (rather than IDLDE) prompt, so I do the following IDL> !path = !path + ":/usr/users/Bowler/idl" IDL> print, !path {the path does, indeed, include my directory} IDL> anyData, "data.xxx", inbounds and it says % Attempt to call undefined procedure/function: 'ANYDATA'. % Execution halted at: $MAIN$ Why??? This is 5.0.2 on a Sparc 5 running Solaris 2.5.1. -- Bruce Bowler, Research Associate 207.633.9600 (voice) Bigelow Laboratory for Ocean Sciences 207.633.9641 (fax) PO Box 475 BBowler@bigelow.org (email) West Boothbay Harbor ME 04575 http://www.bigelow.org/
Re: How do I get IDL to see that my procedure exists?
Robert S. Mallozzi (mallors@crazyhorse.msfc.nasa.gov) writes: > I also ran across this with automatic object/struct > definitions. It seems to me to be an unneccessary limitation > that one must name an object something like > > objwithlongname__define.pro > > instead of > > objWithLongName__define.pro Well, I can do whatever I like on *my* computer system. ;-) Cheers, David ---------------------------------------------------------- David Fanning, Ph.D. Fanning Software Consulting E-Mail: davidf@dfanning.com Phone: 970-221-0438, Toll-Free Book Orders: 1-888-461-0155 Coyote's Guide to IDL Programming: http://www.dfanning.com/
In article <MPG.10576deb16a589f598968d@news.frii.com>, davidf@dfanning.com (David Fanning) writes: > Bruce Bowler (bbowler@bigelow.org) writes: > >> I wrote an IDL procedure to do what I want. I put it in a directory >> called /usr/users/Bowler/idl and called it anyData.pro. The first line >> of the file is >> . >> . >> . > > Well, Sir, you are working on an operating system that is > case sensitive. Thus the file "anyData.pro" is different from > a file named "anydata.pro". As it happens, when you type a > name of a procedure at the IDL command line: > > IDL> junk > > and IDL has to go looking for a file with that name > (ie. junk.pro), it *always* looks for files with > lowercase names. > > Name your file "anydata.pro" and you will be in business. > I also ran across this with automatic object/struct definitions. It seems to me to be an unneccessary limitation that one must name an object something like objwithlongname__define.pro instead of objWithLongName__define.pro -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~ Robert S. Mallozzi 256-544-0887 Mail Code ES 84 Work: http://crazyhorse.msfc.nasa.gov/ Marshall Space Flight Center Play: http://cspar.uah.edu/~mallozzir/ Huntsville, AL 35812 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~