GNU bug report logs -
#345
Bug in F90 mode
Previous Next
Reported by: Gabor Toth <GTOTH <at> UMICH.EDU>
Date: Sun, 1 Jun 2008 14:05:05 UTC
Severity: normal
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
This is an automatic notification regarding your bug report
which was filed against the emacs package:
#345: Bug in F90 mode
It has been closed by Glenn Morris <rgm <at> gnu.org>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Glenn Morris <rgm <at> gnu.org> by
replying to this email.
--
345: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=345
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Gabor Toth wrote:
> The bug is present in every version of emacs I know of.
I can't reproduce it in Emacs 21.4, 22.1 or 22.2.
(The CVS trunk does have a separate problem here; funny coincidence.)
> (defconst f90-type-def-re
> "\\<\\(type\\)\\([^(\n]*\\)\\(::\\)?[ \t]*\\b\\(\\sw+\\)")
This form was replaced 6 years ago, ie in Emacs 21.3.
I strongly advise you to use a more recent version of Emacs (the
latest is 22.2), where we have the equivalent of:
(setq f90-type-def-re "\\<\\(type\\)\\>\\(?:[^()\n]*::\\)?[ \t]*\\(\\sw+\\)")
[Message part 3 (message/rfc822, inline)]
Dear GNU emacs developers,
I truly appreciate the work put into the emacs editor. This is the
editor of choice for editing source code files because of the many
advanced features that help programmers. I have been using the F90
module for a long time and I encountered a small but annoying bug. I
tried to work around it, but I could not.
The bug is present in every version of emacs I know of. It is a bug
in the F90 module. To reproduced the bug, simply create a file
with .f90 extension, say
bug.f90
open the file, and type the following lines
program bug
AnyVariable = 1.0
TypeVariable = 2.0
OtherVariable = 3.0
end program bug
and let Emacs indent it (by hitting TAB at the beginning of each
line). The result is what you see above, ie the lines following the
TypeVariable = 2.0 line are indented.
The reason is that if a line starts withTypeXXX the F90 module
regards it as a type definition, although it is not matched when an
end statement is typed. I suspect that the error is in the definition
of f90-type-def-re in the f90.el file. The definition is
(defconst f90-type-def-re
"\\<\\(type\\)\\([^(\n]*\\)\\(::\\)?[ \t]*\\b\\(\\sw+\\)")
It seems that this regular expression is too permissive. The [^(\n]**
part matches anything that follows the "type" string except for
opening paren and end-of-line. This should probably be replaced with
[ \t]*
I would be greatful if you could suggest a work around that I can put
into my .emacs file. My attempts at redefining the f90-type-def-re
did not work. I managed to set the indentation to 0 for type/
interface/blockdata definitions to avoid this problem, but then the
true type and interface definitions will not be indented, and that's
pretty ugly. We have some huge F90 codes, and not allowing variables
to start with the string "type" is not an option.
Thanks for your work and kind help,
Gabor Toth
Research scientist
University of Michigan
This bug report was last modified 16 years and 355 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.