Fortran 90/95 syntax

[NNemec]

Syntax file for freeform Fortran 90/95

[NNemec]

git patch for f90 syntax

[winnie]

nice new feature.. but this surely don't belong into a bugfix release. Therfore adding milestone 4.7

4.6.X will be only bugfix releases new features will go into 4.7

[slyfox]

I don't know fortran, but it looks like f90 is case insensitive (like pascal or basic).
So provided syntax has hard times highlighting lowercase style.
(tested on first .f90 file in my system: /usr/lib64/python2.5/site-packages/numpy/f2py/docs/usersguide/moddata.f90)

The rest looks ok.

[NNemec]

True, Fortran is generally case-insensitive. Checking pascal.syntax I find that there does not seem to be a straightforward way to specify case-insensitive keywords in mcedit? I'm not really excited about the idea of putting various versions of each keyword in the syntax file. Any ideas about that?

Replying to slyfox:

I don't know fortran, but it looks like f90 is case insensitive (like pascal or basic).
So provided syntax has hard times highlighting lowercase style.
(tested on first .f90 file in my system: /usr/lib64/python2.5/site-packages/numpy/f2py/docs/usersguide/moddata.f90)

The rest looks ok.

[ossi]

Replying to NNemec:

I find that there does not seem to be a straightforward way to specify case-insensitive keywords in mcedit? [...] Any ideas about that?

you can more or less easily implement a "keyword/i" keyword for that purpose.
for optimization, you might want to require the case-insensitive keywords in the syntax file to be always uppercase, so only the compared text needs to be uppercased.

[ossi]

Replying to ossi:

for optimization, you might want to require the case-insensitive keywords in the syntax file to be always uppercase, so only the compared text needs to be uppercased.

actually, that's stupid. the syntax reader can do that optimization internally, as the file is read at startup.

[NNemec]

Right now, I do not have the time to dig through the C sources of mc to implement this. Maybe someone who already is acquainted with the sources could do that with much less effort?

Replying to ossi:

you can more or less easily implement a "keyword/i" keyword for that purpose.
for optimization, you might want to require the case-insensitive keywords in the syntax file to be always uppercase, so only the compared text needs to be uppercased.

[slyfox]

Ok. Then we can just add current f90.syntax and enhance it when something like IGNORECASE directive will be added to syntax engine.

My vote