I'm working in an AREV 3.12 application. I've updated a program (added more error messages and documentation and cleaned it up a bit) but when I go to compile it, I get the message: "Label 'CREATE_CREDIT_CARD_PO' is missing." along with a line number. I've checked that GOSUB calling this routine and the label for this routine are both spelled the same.

The line number given is well before the line number that the routine label is at within the program.

I've check other things like LOOPs missing a REPEAT or a FOR missing a NEXT or an IF missing an END and the like and haven't found a problem there.

I'm able to compile the original code where the number of lines and/or characters between the GOSUB and the routine label are slightly less.

Is there a maximum number of lines and/or characters between a GOSUB and the routine label beyond which the compiler can't see the label and thus the message above?

So far I haven't found anything within this discussion area that touches on this.

Can anyone point me in the right direction?

Thanks,

Michael Slack

Do you have OI9+, you could paste the code in there and do a reformat to check if there is a missing END statement.

Or, you could email me the code barry@bsbsoft.com.au and I can have a look for you, 4 eyes better that 2

You could have too many end statements. Use the BLIST command at TCL to format the code and see.

Hello Barry:

I only have access to AREV 3.12.  Our management hasn't had us make the move to OI for various reasons.

A missing END was one of the first things I checked.  The way I did that was to print the program to a text file which gave me indentation marks (|).  That gave me an easy and visual way to make sure everything matched up.  I could easily verify that an 'IF' had and 'END", a 'FOR" had a 'NEXT', a 'LOOP' had a 'REPEAT" and so on.

Thanks,

Michael Slack

Hello Warren:

BLIST is something I'm going to have to look up.  I'll give it a try but I checked that by way of printing the program to a text file and used the indentation marks (|) to look for missing ENDs, NEXTs, REPEATs and so on.  It doesn't mean I didn't miss something.

Thanks,

Michael Slack

There is some maximum size for source code, including all $inserts.

So, you may have to split some code to another subroutine instead of

using a GOSUB.

Try temporarily removing a block of lines before this addition and see if it compiles without error. Otherwise, I'd look again at that LISTBASIC output.

Dave

Thanks for pointing me in the right direction. It turns out that I wasn't missing a END but had and extra END because I was missing an ELSE.

Part of what I did for this particular program was add error messages where there wasn't any. It turns out, on a WRITE statement where I did this, I forgot to add the ELSE to it. Thus I had an extra END that was the cause of the problems until I corrected the statement.

Thanks for your help. I was on my third pass thru the program looking for a missing END or something when I found my problem. You saved me a lot of hair tearing and whatnot.

Michael Slack

Consider indenting like BLIST does.

I don't actually use gosub as a program statement.

I'm more worried about the minimum distance between GOSUB and a label.

Reminds me of a long time ago using the RevG text editor. I would enter, say a IF statement. I would proceed to immediately enter the END ELSE (if used) and the END statement. Then I'd up-arrow to the original IF statement line end open a blank line for the "true" statements.

Still do this decades later, with 2 space indents (hate them tabs).

I don't need no stink'n editor that does that for me, or "Automatically closes braces"!

The Automatic close brace drives me nuts…

View this thread on the forum...