END IS...
#1
You know the feeling - I had this large code in a function, lots of Select Case and IF/END IF's nexted in each other and I was 100% sure I had done everything according to the book, but it didn't compile. "Select expected", pointing at a final End Select at bottom of the function.

I checked everything - All IF's had a matching END IF and all Select cases had a matching End Select. Checked all For/Next loops, each line of code and all looked ok, but still "Select expected"from the compiler. Brain freeze - I had to leave it at that and go for a walk, eat some dinner and when I got back, I carefully read through each line of code - and finally found the faulty line - I had written "END IS" in the middle of everything, but the compiler of course went on reading the code until the end of it before it reported the error. I know that's the way it works.

Stupid error - changed IS to IF and al is well again. Beginning to wonder if it was a Freudian Slip from my fingers and the END really IS here for my brain..  Cool
Reply
#2
Hi Borje
to this day I have problems with nested If then Else If constructs, it's especially troublesome in Pascal
Reply
#3
(Yesterday, 17:00)Borje Hagsten Wrote: You know the feeling - I had this large code in a function, lots of Select Case and IF/END IF's nexted in each other and I was 100% sure I had done everything according to the book, but it didn't compile. "Select expected", pointing at a final End Select at bottom of the function.
<snip>
Stupid error - changed IS to IF and al is well again. Beginning to wonder if it was a Freudian Slip from my fingers and the END really IS here for my brain..  Cool

For me, it's almost always something like this:

Code:
if x = 0 then
x += 1
end fi

My eyeballs run over it, see two "words" in the line starting with "END", and don't register the problem.  If course, it's lever at the 1st or 2nd level of nesting.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)