i'm going to say the exact opposite of Beavis.
includes, if i understand it correctly, are going to be deprecated and should not be used in dbp.
make sure you're not using them and only include files by the method you described above (adding them through the IDE).
sometimes it's not really related to the exact command, but rather to the implementation and misinterpretation of some other piece of code. here are some things that trip up the compiler:
- having a function or type at the top or bottom of an included source file. try putting a comment at the top or bottom
- duplicate function names in different include files
- having a funtion paramater, a constant or a global named the same. there were previous problems with having partly similar names, but i believe these have been resolved since patch 3 (ie. #constant var and global variable would trip up the compiler because it would see the 'var' in 'variable')
also, for clarity, you might want to try typing out your function parameters:
FUNCTION MakeSkyBox(id AS INTEGER, range# AS FLOAT)
hope this helps. cheers.
edit: also, one more thing. if you have a function earier in your source that is missing an ENDIF or an ENDWHILE etc. then this might be confusing the compiler and giving you an incorrect error message as well, EVEN IF the confounding source is in a DIFFERENT source file. check to make sure you're not dangling participles.
-= i only do what my rice krispies tell me to do =-