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

Home » Public Forums » archive » Re: arrays vs. functions conflicts
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: arrays vs. functions conflicts [message #38391 is a reply to message #38390] Fri, 05 March 2004 05:56 Go to previous messageGo to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Paolo Grigis writes:

> Thus my problem:
> To resolve the conflict {that is, limits.pro being already
> compiled and procedure.pro refusing to compile because it has
> an old-fashioned statement like var=limits(1:2) instead of
> var=limits[1:2]} I'm thinking of automatically compiling
> the (hopefully) few troubling routines like procedure.pro
> at startup using the resolve_routine() statement.
> (BTW, why is the IDL compiler (5.5) not smart enough to
> understand that function(1:2) is an array? ":" is never allowed
> in function calls, after all.)
>
> But before going on, I just wanted to know if there is an
> easier way ouy of this that I have overlooked.

IDL itself could care less about this issue. So if
you are having problems with it then *you* must
care about it. Does you procedure.pro have a compiler
option that forces strict arrays? Then take it out.
Problem solved. :-)

Cheers,

David
--
David Fanning, Ph.D.
Fanning Software Consulting
Coyote's Guide to IDL Programming: http://www.dfanning.com/
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Widgets in VM
Next Topic: How to get info about ROI from iTools IIMage?

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

Current Time: Wed Oct 08 15:47:05 PDT 2025

Total time taken to generate the page: 0.00458 seconds