| Re: endi and endif [message #85062 is a reply to message #84870] |
Fri, 28 June 2013 05:49  |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Saturday, June 15, 2013 12:27:25 AM UTC+2, Jeff N. wrote:
> On Friday, June 14, 2013 5:21:35 PM UTC-4, Chris Torrence wrote:
>
>> On Friday, June 14, 2013 3:16:47 PM UTC-6, wlandsman wrote:
>
>>
>
>>> On Friday, June 14, 2013 5:01:56 PM UTC-4, ri...@crd.ge.com wrote:
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> I get the expected "endif" on my system.
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Thanks, I've discovered that my workbench editor ( { x86_64 darwin unix Mac OS X 8.2.3 May 2 2013 64 64} ) can get into a mode where the final "f" is really there but not visible. Then when I add my own "f" it becomes "endiff" and no longer compiles. This doesn't always happen but has happened several times in the past few months.
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> An alternative explanation is that I've started hallucinating. I haven't completely ruled this out yet, but if true I hope I would have had more interesting hallucinations. --Wayne
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> IDL> help, !version
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> ** Structure !VERSION, 8 tags, length=104, data length=100:
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> ARCH STRING 'x86_64'
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> OS STRING 'Win32'
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> OS_FAMILY STRING 'Windows'
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> OS_NAME STRING 'Microsoft Windows'
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> RELEASE STRING '8.2.3'
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> BUILD_DATE STRING 'May 3 2013'
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> MEMORY_BITS INT 64
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> FILE_OFFSET_BITS
>
>>
>
>>>
>
>>
>
>>>>
>
>>
>
>>>
>
>>
>
>>>> INT 64
>
>>
>
>>
>
>>
>
>> Hey Wayne,
>
>>
>
>> That's really cool. I've never heard of this bug. If you could let us know what you are doing to get into this state, that would be helpful. Not the hallucinating state, just the Workbench state.
>
>>
>
>> -Chris
>
>
>
> For what it's worth, this has happened to me before also. I didn't save any details of what i was doing or anything, so i can't recreate it (helpful i know!), but i do remember it happening. I'm pretty sure i had to restart IDL to get it to compile with "endif" and not "endi".
>
>
>
> Jeff
Hi,
the same just happened to me, but with the R in ENDFOR.
So the workbench displays
FOR j=0,N_ELEMENTS(SubSet)-1 DO BEGIN
...MY LOOP IN HERE...
ENDFO
And it compiles. If I add an F to ENDFO, it does not compile and throws an error. Furthermore the color of the ENDFO is switched from that of a control statement to that of a normal variable.
IDL> print, !version
{ x86_64 Win32 Windows Microsoft Windows 8.2.3 May 3 2013 64 64}
Has anybody any insight in how this happens and how one gets rid of it?
This happened after a lunch break. The pc was in sleep mode in the meanwhile.
Cheers,
Helder
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
