http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45786
Daniel Franke <dfranke at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dfranke at gcc dot gnu.org
--- Comment #6 from Daniel Franke <dfranke at gcc dot gnu.org> 2010-12-16
00:25:54 UTC ---
Shot in the dark, isn't this related to ...
typedef enum
{ [...]
/* ==, /=, >, >=, <, <= */
INTRINSIC_EQ, INTRINSIC_NE, INTRINSIC_GT, INTRINSIC_GE,
INTRINSIC_LT, INTRINSIC_LE,
/* .EQ., .NE., .GT., .GE., .LT., .LE. (OS = Old-Style) */
INTRINSIC_EQ_OS, INTRINSIC_NE_OS, INTRINSIC_GT_OS, INTRINSIC_GE_OS,
INTRINSIC_LT_OS, INTRINSIC_LE_OS,
[...]
}
gfc_intrinsic_op;
... which was introduced to ...
(In reply to comment #5)
> IIRC, it used to be that way but it was changed to emit better diagnostics.
Hence
(In reply to comment #1)
> interface operator(.eq.)
> module procedure eq_foo
> end interface operator(==)
would be begun with INTRINSIC_EQ_OS as operator and closed with INTRINSIC_EQ?!
If the one style is silently converted to another style during parsing, the
above could be undone?
