The editor is flagging my own defines as errors (red cross in the side of the line and in the problems panel), even though I can't go to definition by F3 or open declarations.
The most common cause of this error is that the SVE indexer hasn't read the file containing the definition when it compiles the file. Common errors include:
Check the argument file (typically a .f file) for errors. This is the most common error. It could be a path that needs to be checked, or an environment variable that needs to be set
Check that the file is included in the indexer. The file will have a blue dot on it if the indexer is parsing it in the Project Explorer view
You may need to unravel your compilation process to make sure that the defines are read before they are used (if not the define won't be availalbe for the SVEditor to parse and show the error you are seeing).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually it was a .f issue: I didn't know that the parser checks the include inside a packages and adds it automatically, so I was adding the files my self one more time. (so they are duplicate)
I had to remove files that are already included the packages. and now that is fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
EDIT: even though I CAN go to definition by F3 or open declarations. (the open declartion works perfectly)
Last edit: Safouan Ben Jha 2017-03-28
Safouan,
The most common cause of this error is that the SVE indexer hasn't read the file containing the definition when it compiles the file. Common errors include:
Thank you for the answer.
Actually it was a .f issue: I didn't know that the parser checks the include inside a packages and adds it automatically, so I was adding the files my self one more time. (so they are duplicate)
I had to remove files that are already included the packages. and now that is fine.