Programming with dBASE - Compiling deo app

Author

Compiling deo app

Rick

2006-03-07, 1:23 pm

I have a very large app, and like to tie up my if...endif by including the condition on the end of the endif.

if thisworks
endif thisworks

Of course, the compiler never likes the ENDIF thisworks and reports a warning every time it runs into anything after the endif.

It has not been a problem up till now, but I get a compiler error that the symbol table is full and the compile stops. When I got this message before, it was because one of the object files had a bug in the code. Now it appears the accumulation of warni
ng messages may be causing it.

Anyone know if I am right in assuming that this symbol table the compiler refers to includes is choking on too many warning messages?

I am able to get around it by splitting the project file into 2 files, and my deo files are compiled to the proper location. But guess I would like to know if others have found this to be necessary, or there may be something else I am overlooking here.

Thanks,
Rick

Mervyn Bick

2006-03-07, 8:23 pm

On Tue, 07 Mar 2006 21:29:03 +0200, Rick <Sportman7@netzero.com> wrote:

> I have a very large app, and like to tie up my if...endif by including
> the condition on the end of the endif.
>
> if thisworks
> endif thisworks
>
> Of course, the compiler never likes the ENDIF thisworks and reports a
> warning every time it runs into anything after the endif.

Have you tried marking the bit after the endif as an in-line comment?
ie endif // thisworks
This won't upset the compiler and will still enable you to keep track of
the code.

Mervyn

Rick

2006-03-08, 3:23 am

Mervyn,

Yes that is true. Just from habit I usually copy the if code line down to the endif. Guess I should add another step and comment out the code after the endif. Do not understand why the compiler needs this warning on endif lines since it has no conseque
nce for runtime.

Thanks,
Rick

Mervyn Bick Wrote:

> On Tue, 07 Mar 2006 21:29:03 +0200, Rick <Sportman7@netzero.com> wrote:
>
>
> Have you tried marking the bit after the endif as an in-line comment?
> ie endif // thisworks
> This won't upset the compiler and will still enable you to keep track of
> the code.
>
> Mervyn

Sponsored Links