[photran-dev] Change to Photran content types, MBS extensions

[Jeffrey Overbey <overbey2@xxxxxxxxxxxx>]

Hi Bill--  (c photran-dev, for the record)

I just committed a fairly large change that completely changes how we
handle the various source forms in Photran.  Instead of having
separate content types, there is only one
(org.eclipse.photran.core.fortranSource) and the distinction between
the various source forms (fixed, free, C preprocessed free, etc.) is
handled via project properties.  It's a lot more flexible this way
(cf. Bug 309045).

Anyway, the MBS toolchains were all using hard-coded filename
extensions (since CDT couldn't handle multiple content types), but
since we have only one content type now, that's no longer an issue.

I commented out the part of plugin.xml in
photran.managedbuilder.intel.ui that was using hard-coded extensions
and changed it to use content types instead (lines 1470-1481).  It
looked identical to the same parts of the GNU and XLF toolchains,
which I changed as well.  However, I don't know that code very well,
so if that was wrong -- if it's going to introduce some problems for
you -- then please let me know, and I'll change it back.  (The thing
I'm particularly unsure about is what will happen if you define a
non-standard filename extension, like *.weirdfor, and associate it
with the Fortran content type.  I'm not on a Linux machine at the
moment, or I'd try it out with the Intel toolchain myself.)

Jeff