|
forums.silverfrost.com Welcome to the Silverfrost forums
|
View previous topic :: View next topic |
Author |
Message |
Rainer
Joined: 13 Mar 2006 Posts: 43
|
Posted: Wed Mar 29, 2006 4:47 am Post subject: Sparse information from compiler & linker |
|
|
Hi,
I've just upgraded to the most recent version of FTN95 (4.9.0 I think) and noticed that both compiler and linker still give very little information on the precise location of a problem they spotted.
For example, when using the "%" symbol with yet undeclared derived types, the compiler tells me the line, but not the particular variable that caused the problem. In lines with several derived types, this means I have to check each one separately, when the compiler could have easily given me that additional information. If it didn't have that information it wouldn't have spotted the error in the first place, right ?
Or the linker tells me about missing symbols, but doesn't give the line or even the file/module where the symbol is unknown. In my case it just always names the main object file as location. Same situation here, but sometimes even more work to search for the problem.
I'd like to ask whether in future versions of the FTN95 compiler there is going to be more information on the location of errors.
Thanks,
Rainer
|
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Wed Mar 29, 2006 8:33 am Post subject: Sparse information from compiler & linker |
|
|
Rainer
The short answer to your question is no, there is unlikely to be significant improvement in these areas in the short to medium term.
For missing symbols, you could use "Find in files".
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|