Re: etags confused with uppercase filenames (on Windows)

[Francesco Potorti` <pot@gnu.org>]

   Does it really make sense to have etags behavior be different on
   different platforms?  Especially given the fact that some file you are
   working on can well come from a Windows system that exports its
   filesystem?

I partly agree with Stefan's observations.  I am inclined towards
implementing the following behaviour for etags when determining
languages.  Each line is considered only if the previous ones did not
yield any match.

1) use the explicitely given language, if any
2) guess it from the file name (usually from the suffix)
3) guess it from the #! interpreter
4) if file name is all upcased, guess it from the file name without
   regard to case (usually from the suffix)
5) try Fortran and give a warning if succeded
6) try C/C++ and give a warning (always succeeds)

The differences from the current behaviour are that 4) does not
currently exists, and 5) and 6) do not currently elicit a warning.
   
Note that 3) is currently used for Perl only, even if other languages
using #! may be added in the future.

Note also that this behaviour is independent of the platform.