topic No. When a solution is opened in Intel® Fortran Compiler

Intellisense language parsing

Simon_Geard — Wed, 05 Dec 2012 15:18:42 GMT

Is it possible to run the language parser separately? I ask because the code I'm working on has at least one file that causes VS 2010 to crash whilst it is being parsed. I have turned the feature off so I can work but I'd like to identify which files are causing the problem.

Thanks,

Simon

No, it isn't. We are aware

Steven_L_Intel1 — Wed, 05 Dec 2012 15:51:16 GMT

No, it isn't. We are aware of two situations that can trigger this problem, both dealing with fixed-form source with continued source lines. 1. An operator such as .LT. is split across source lines 2. Splitting a Hollerith constant (such as 10HABCDEFGHIJ) across source lines Both will be fixed in Update 2, planned for late January.

I've checked the file on

Simon_Geard — Wed, 05 Dec 2012 16:16:51 GMT

I've checked the file on which the parser had stopped immediately prior to the crash and it is (1) above, so I'll wait for update 2. Thanks, Simon

Can't you just edit the

Steven_L_Intel1 — Wed, 05 Dec 2012 16:21:33 GMT

Can't you just edit the source to readjust where the line splits? Or is this all machine-generated code?

The problem is that there are

Simon_Geard — Wed, 05 Dec 2012 17:00:04 GMT

The problem is that there are actually quite a lot of files which have this type of line. Not great coding I agree, but it is the way code was written years ago. For us it is a real plus to have found out why Visual Studio kept crashing and be able to stop it, but I'm fairly sure I won't be allocated time to trawl throught all the fixed-format code looking for this type of construct - particularly if it's going to be fixed at the next update. Simon

If it's just VS, can't you

lklawrie — Wed, 05 Dec 2012 21:11:40 GMT

If it's just VS, can't you use the command line version of the compiler?

No. When a solution is opened

Simon_Geard — Thu, 06 Dec 2012 09:19:22 GMT

No. When a solution is opened VS automatically starts parsing all the files in the solution to build its intellisense database; it is that operation that is causing VS to crash when it encounters one of these files. The file itself compiles without problem.