| Re: Problem running functions [message #85819 is a reply to message #85818] |
Wed, 11 September 2013 17:15   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
laura.hike@gmail.com writes:
> Yes, I restart every time because sometimes crap gets stuck in the memory. You don't know how many times I tried running down an error that was easily solved by restarting.
Well, it is true that if you ever call a technical support engineer the
first thing they will ask you to do is restart IDL, but it is not really
because it solves 50% of the problems people call in with. It is because
it gives them a fresh start in understanding what the real problem is.
If you find yourself restarting IDL often, something is seriously wrong
with IDL or with the way you are using it.
> I also have separate directories for each of my projects. Sorry if you don't like that.
Oh, I like it. This is how I organize my life, too. I was just offering
you the simplest solution that was sure to work. Once you know how to
put directories on your IDL path (and this is NOT the way you were
formerly doing it), you can put directories of programs anywhere you
like. IDL will find them, and compile them successfully, if it knows
where to find them.
> Aside from solving all my life's problems, do you have an answer to
the original question? I don't understand why procedures always run
correctly from my idl subroutine directory but functions don't. I'd
still like to know the answer whether I change my ways or not.
My guess is, your programs are named incorrectly and/or then can't be
found AND you are not using the STRICTARR compile option so that IDL can
tell the difference between a function call and an array subscript.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
