#include

The literature says nothing about the location of the directive #INCLUDE filename.basinc within a source file.

Does it matter where it is located?

Does it work? The Manual says:
#include “filename”
Include code from a separately saved file within this program.
Example: #include “c:\test.bas”
NOTE: Reserved for future use. Not currently implemented.

So that last statement suggests there are issues, but if it did work, I'd expect to 'include' it where I wanted the code to be inserted in the main code.

#include will insert text at that exact point

eggdweather said:

NOTE: Reserved for future use. Not currently implemented.

So that last statement suggests there are issues, but if it did work, I'd expect to 'include' it where I wanted the code to be inserted in the main code.

Click to expand...

The manual is not as up-to-date as the on-line reference. Click on "BASIC Commands" at the top of this forum; select Directives and lookup #include. No mention of it not being currently implemented.

pe6.pdf

page 21

As the compiler processes ’top-to-bottom’ on the pre-processor output file it is necessary to take care to ‘skip’ the #INCLUDE file (if necessary) when it is included at the top of a program.

Click to expand...

Thanks, Technical. This is the kind of thing that is missed over and over in the manuals. I hope it gets better.


PS. The other answers missed the question completely. You actually have to read what people write. Nice try.

Texasclodhopper said:

PS. The other answers missed the question completely. You actually have to read what people write. Nice try.

Click to expand...

You said

The literature says nothing about the location of the directive #INCLUDE filename.basinc within a source file.

Click to expand...

The literature does say something about its location in pe6.pdf page 21.

You ask

Does it matter where it is located?

Click to expand...

The quote from pe6.pdf gives one example where it may matter.

You can lead a horse to water, but you can't make it drink.

tarzan said:

The literature does say something about its location in pe6.pdf page 21.
The quote from pe6.pdf gives one example where it may matter.

Click to expand...

And worth noting that if the include file is in the 'wrong' place you will get an error.

This is not saying where the #include file should be located ... so more is needed.

... As the compiler processes ’top-to-bottom’ on the pre-processor output file it is necessary to take care to ‘skip’ the #INCLUDE file (if necessary) when it is included at the top of a program.
Reset_here: Goto Init #INCLUDE “sphero.basinc” Init:
; jump over include file
; start program here

Click to expand...

Thus the reason for my question. I didn't get an error. My program just didn't work as expected.

srnet said:

And worth noting that if the include file is in the 'wrong' place you will get an error.

Click to expand...

Actually, you can't always lead a horse to water, and you can make them drink if you can lead them there. I know.

A #INCLUDE directive can be placed anywhere you want, however you may need to consider the consequences of where it is placed.

If the #INCLUDE file includes a SYMBOL definition used by your program the #INCLUDE has to be before that symbol is used or it won't have been defined when it is used, will generate an error.

Likewise though, if the #INCLUDE file includes an END statement and you include it before your main program then that will get executed unless you take care not to execute it and execution will never reach your own program.

Using #INCLUDE is effectively doing a copy-and-paste of the text in the #INCLUDE file to where the #INCLUDE directive appears.