comp.lang.idl-pvwave archive: archive » quirk End of file encountered before end of program

Home » Public Forums » archive » quirk End of file encountered before end of program

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: quirk End of file encountered before end of program [message #89868 is a reply to message #89867]

Fri, 12 December 2014 06:38

lecacheux.alain
Messages: 325
Registered: January 2008

Senior Member

On Friday, December 12, 2014 2:38:52 PM UTC+1, LC's No-Spam Newsreading account wrote:
> On Thu, 11 Dec 2014, Jim P wrote:
>
>>> The code should look something like this
>>>
>>> pro xxx.pro,ARGUMENTS
>>> openw,2,'temporary.temp'
>>> printf,2,'structure=create_struct( $'
>>> CASE STATEMENT FILLING THE STRUCTURE DEFINITION in the temp file
>>> printf,2,')'
>>> close,2
>>> ; and instantiate it
>>> @ temporary.temp
>>> return
>>> end
>
>> I suspect this isn't behaving as you wish it to behave, due to a
>> misinterpretation of how "@" is used.
>>
>> The "@" in your code is interpreted at compile time, not at run time.
>
> I did not realize that.
>
> The original code I had (dating to several years ago, before anonymous
> structures were introduced) used in fact a much more complex mechanism.
>
> It wrote the structure definition (without use of CREATE_STRUCT which
> did not exist) to the temporary.temp file
>
> then wrote a xxxtmpnnn.pro file with nnn increasing each time, which
> contained the invocation of @temporary.temp (and passed back the
> created structure as argument)
>
> then built a string with the invocation of xxxtmpnnn.pro
> and used execute to invoke it
>
> When I did now some simple tests, I thought that the above arrangement
> was become unnecessary now with create_struct and anonymous structures.
> I wanted to simplify it and hoped it were NOW possible.
>
>
> Apparently I cannot do execute('@temporary.temp')
>
> Is there any limitation to the string length in execute(string) ?
>
> I used a temporary file because the structure definition is rather long,
> and is constructed in steps (driven from a data file) ... for legibility
> temporary.temp has the statement on several lines (terminated by the $
> continuation marker but last one)
>
> If there is no limitation I could concatenate the pieces of the
> statement instead of writing them to temporary.temp and just execute the
> resulting string.

if you do not want to initialize your structure directly in the main procedure (by x = {...}), you could create an external function 'fun.pro' like:
function fun
x = {...}
return, x
end
and call it, from the main procedure by x = call_function('fun').

alx.

Report message to a moderator

[Message index]

		quirk End of file encountered before end of program By: LC's No-Spam Newsread[1] on Thu, 11 December 2014 07:03
		Re: quirk End of file encountered before end of program By: Jim Pendleton on Thu, 11 December 2014 07:45
		Re: quirk End of file encountered before end of program By: LC's No-Spam Newsread[1] on Fri, 12 December 2014 05:38
		Re: quirk End of file encountered before end of program By: lecacheux.alain on Fri, 12 December 2014 06:38
		Re: quirk End of file encountered before end of program By: LC's No-Spam Newsread[1] on Mon, 15 December 2014 03:42
		Re: quirk End of file encountered before end of program By: Yngvar Larsen on Mon, 15 December 2014 07:05
		Re: quirk End of file encountered before end of program By: LC's No-Spam Newsread[1] on Wed, 17 December 2014 02:28
		Re: quirk End of file encountered before end of program By: lecacheux.alain on Wed, 17 December 2014 08:49
		Re: quirk End of file encountered before end of program By: Yngvar Larsen on Wed, 17 December 2014 23:57

Previous Topic:	reading binary file with READ_BINARY
Next Topic:	IDLgrPolygon question

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 19:34:03 PDT 2025

Total time taken to generate the page: 0.00420 seconds