comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: .compile_opt strictarr is persistent?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: .compile_opt strictarr is persistent? [message #50587 is a reply to message #50586] Mon, 09 October 2006 11:32 Go to previous messageGo to previous message
Michael Galloy is currently offline  Michael Galloy
Messages: 1114
Registered: April 2006
Senior Member
David Fanning wrote:
> Craig Markwardt writes:
>
>> Should I put the .compile_opt statement *within* each individual
>> function in the module?
>
> Absolutely. I'm not sure where you are using the
> compile_opt statement (no period in front of it,
> by the way), but if you use it at the IDL main
> level, it is defined at the main level. If you
> want it in effect inside procedures and functions,
> it will have to be declared inside each and every
> procedure or function you want to use it in.
>
> Done this way to ensure backward compatibility, not
> to make your life easier. :-)

Follow David's advice as above. I did try this because it seemed odd
behavior you were describing. IDL does not complain if you have a
compile_opt statement outside of any routine in a file. It will change
the behavior of the main-level (but not the routines in the file). I
think I will make a list sometime of the most dangerous things IDL will
let you do.

Mike
--
www.michaelgalloy.com
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Low pass filter - Problem with kernel
Next Topic: string functions and arrays

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 15:49:09 PDT 2025

Total time taken to generate the page: 0.00420 seconds