Problems in editor enhancments

[abhimodak]

Hi

The editor enhancements have been a nice surprise. Must say the cliched -- very late; but late is better than never. I had already written a few macros in VB (with string parsing) to do this stuff and although time spent on that is now useless, Intel's implementation of editor enhancements indeed makes IVF a pleasant experience. In my opinion, certainly increasesthe overallvalue.

However,a few bad behaviors are outlined below. A quick fix to these would be great. Some (see below) are broken since update 5.

{In VS2010 Tools --> Options --> Text Editor --> Fortran --> Advanced, set all choices except Disable Database and Scan system includes to True.}

Editor enhancements need an open project for a file with .f90 extension (haven't tried for *.f or *.for)

(1) Open Visual Studio 2010. Use File --> New File --> IVF --> Fortran Free-form --> Open. This will open a new file with default name Source1.f90.
(2) Write some dummy program.
(3) There is syntax coloring but all other (relevant) editor enhancements are gone. For example, there will be no outlining, no navigation-bar at the top of the file. I wrote "relevant" because things such as "go to definition" can (should?) be project dependent and hence not available. But there is no reason for features such as outlining, intrinsic function help to be project dependent.
(4) Save and close the above file and exit visual studio.
(5) Re-open VS and open an existing Fortran solution.
(6) DO NOT add the previous source file to this project. Simply open it through File --> Open.
(7) Some editor enhancements appear to be working; this includes outlining for some (programs, subroutine etc), help on intrinsics, adding snippets, and even "goto definition". However, outline for do, if etc. does not happen. {The "go to definition" presumably gets restricted to the given source file.}

Behavior for file with .f95 (or other user specified) extension

These extension are added through Tools --> Options. (Note that the editor enhancements such as syntax coloring have already been broken by update 5; see http://software.intel.com/en-us/forums/showthread.php?t=85048&o=a&s=lr.)

While at least some editor enhancement appear when an .f90 file (NOT added to the project) is opened with the project as mentioned in step A6,in the case ofuser-defined file extensions, no editor enhancements happen until the file is added to the project. When the file is added to the project, all editor enhancements seem to be working.

Command line executable in visual studio

(1) Create some dummy source file and compile it at IVF command line with "ifort myprogram.f90" to create myprogram.exe
(2) Type devenv myprogram.exe. This should open VS2010 with myprogram.exe.
(3) Due to behavior mentioned in and above, no editor enhancements are available except for some basic syntax highlighting and that too only for .f and .f90 files.

Highlight Matching tokens
The tooltip here mentions "enclosing braces" but I do not see it happening at all. (Highlighting of blocks such as "do end do" correctly works.

After adding a "snippet" the "tab" key does not work on the next white line or any subsquent white lines until a white line is added.

(1) In the source file of a project, type sub and hit TAB. This will insert a block for subroutine sub. The name sub with be highlighted. Type "method" instead of sub.
(2) Press down arrow (or click on the next line). The line will be "! Variables".
(3) Press down arrow once more to be in the "white space" line between "! variables" and "! Body of Method". Hit TAB here. No indentation will occur.
(4) Same is true for the while line between "! Body..." and "end .."
(5) The TAB key will start to work only after something is typed in the white lines or after a white line is inserted.

There is no outlining for "type".
I see a possible reason here being that type is also used to declare entities (within a type itself) and it may be difficult to resolve type ..end type.

Abhi

[Steven_L_Intel1]

Thanks for the comments - I will pass these on. Yes, the tip for matching tokens should not mention braces.