Bug 286446 - Changes needed to support the C preprocessor
Summary: Changes needed to support the C preprocessor
Status: RESOLVED FIXED
Alias: None
Product: PTP
Classification: Tools
Component: Photran.For Internal Use (show other bugs)
Version: 4.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: 6.0   Edit
Assignee: Jeffrey Overbey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 304430 309043 290209 305576 309045
  Show dependency tree
 
Reported: 2009-08-12 16:28 EDT by Jeffrey Overbey CLA
Modified: 2010-04-13 16:02 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Overbey CLA 2009-08-12 16:28:09 EDT
1. PhotranTokenRef objects use IFiles, workspace-relative paths, and file offsets; this should be changed to use stream offsets instead.

2. User actions (Refactor, Search, etc.) use SourceForm.UNPREPROCESSED_FREE_FORM and respond with "the file in the editor cannot be parsed" when macros are used.  This source form may be used elsewhere.

3. The user should be able to configure (in the GUI) which filename extensions correspond to preprocessed files and which ones do not.

4. There is no option to preprocess fixed-form files (either as CPP or to handle Fortran INCLUDE lines).

5. When the C preprocessor is run, Fortran INCLUDE lines are not handled.  It needs to be possible to chain preprocessors.

6. The SourceForm extension point expects 0 or 1 contributions in order to support CPP.  If more preprocessors are available, the user should be able to select one and/or chain them together.
Comment 1 Jeffrey Overbey CLA 2009-12-08 15:45:24 EST
Items 3 and 6 are fixed in CVS.  There are now separate (sub-)content types for C preprocessed free and fixed form Fortran, and the sourceForm extension point was changed to specify a content type.
Comment 2 Jeffrey Overbey CLA 2009-12-08 15:46:28 EST
There is also a new user action File > Show Preprocessed Source which will show the output resulting from preprocessing the file in the active Fortran editor.
Comment 3 Jeffrey Overbey CLA 2010-03-02 17:22:12 EST
Done except for items 5 and 6.  Ignoring #6 unless there is demand for it.  Filing #5 under a separate bug.