| Re: Compilation Error: Procedure header must appear first and only once [message #94292 is a reply to message #93347] |
Thu, 30 March 2017 14:49   |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Monday, June 20, 2016 at 8:46:15 PM UTC+2, jaromr...@gmail.com wrote:
> I know this question is very old, but this was an error I was getting, and I could not find the solution. I eventually found in my case that this error was caused by a non-printed non-ASCII character at the beginning of the file. After copying the text and saving as a new file (fortuitously without the rogue character) the error disappeared. Subsequent comparisons between the two files revealed the error.
>
> Posting here since this is high on the results lists in internet searches for this error message.
>
> Jarom
>
>
> On Monday, June 27, 2011 at 1:38:42 PM UTC-7, Maegereg wrote:
>> 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?
Hi,
I'll also add to this. I had the same problem and there where no missing "end".
My thoughts:
- this probably only happens if you use the IDLDE.
- this happened to me copying and pasting a file from github.
- between every procedure apparently a hidden character was added. Removing these "empty" lines between procedures solved the issue.
Don't have time test "what" the hidden char is, but it surely happened as a result of the copying from github. I also know that there are other ways to clone into eclipse/IDLDE, but I didn't want to bother...
Cheers, Helder
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
