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

Home » Public Forums » archive » Compilation Error: Procedure header must appear first and only once
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Compilation Error: Procedure header must appear first and only once [message #76737] Mon, 27 June 2011 13:38 Go to previous message
Maegereg is currently offline  Maegereg
Messages: 10
Registered: June 2011
Junior Member
I've been trying to get someone else's program written in IDL 6.4 to
compile in IDL 8.0. I don't have any previous experience with the
language, and my C/Python experience is proving a poor substitute to
expert knowledge. I'm running into the most curious compiler error in
two of my files. I can't put the full code up here (to begin, between
the two there are probably 3000 lines), but I'll try to describe
things as best I can. It's fairly simple: in both of the files, all
the procedures and functions defined past a certain point produce the
following error on compilation:
"% Procedure header must appear first and only once: ANALYZE _ROI_DATA
At:..." (for example). Every function and procedure that's later in a
file than a function or procedure that's got that error gets it too.
And if you were wondering about functions getting an error about
procedures, the functions all also get "Return statement in procedures
can't have values." I've been able to fix it by rearranging the
functions/procedures in a file (worked on one of the two files,
haven't tried it on the other), but I understand there are good
reasons to leave the command procedures/functions at the end of the
file.

I've checked a number of possibilities: these aren't already defined
in the IDL libraries. I checked the procedures immediately before the
first erroneous procedure in both files, and all the begin statements
(and equivalents) seem to have corresponding end statements. The
program compiles fine in IDL 6.4 (I don't have a copy of 6.4, but I've
seen this program run, and have used it myself). I'm just about at the
end of things I can think of to try to fix this. Anyone have any
suggestions?
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Remote plotting
Next Topic: New behavior of n_elements?

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

Current Time: Wed Oct 08 11:01:54 PDT 2025

Total time taken to generate the page: 0.00245 seconds