PR# 15574 Confusing error message if config file has error and does not have .ecf extension

I ran into a problem when writing an eweasel test that was quite confusing
until I figured out what was going on.  If a configuration file does not have
a .ecf extension (this is a guess, based on experiments) but has a syntax
error, compiler reports:

   Parse error: parse error (line 1, column 3)

For the attached config file, the correct error (which is reported if the 
config file has a .ecf extension) is:

   Parse error in Ace.ecf (line 7, column 3): Ace?ecf:7:3:parse error

I assumed the compiler would look inside the file, at least if it didn't have
a .ecf extension, and try to guess whether it was an ECF file or Lace format
based on the contents, which should be pretty easy.

This is mostly a problem with eweasel, where the default configuration file
name is Ace (no .ecf extension).

This problem is fixed in most cases.  The command line compiler reports the
correct error and location for a config file that does not have a .ecf extension.
So does estudio, if the error is introduced after the project is added.

But trying to add a configuration file named Ace which has contents that
looks like a .ecf file but has a syntax error still causes the incorrect error
report.

To reproduce:

Start estudio and try to add the project whose configuration file is named
Ace (use attached file).  Estudio reports:

   Configuration Loading Error
   Unable to load the ace file `/marten/test/Ace'.
   Parse error in /marten/test/Ace (line 1, column 3)

It appears that when *adding* a new project, estudio doesn't try to figure
out if this is an Ace file or a .ecf file.

Reopening report.

David, this issue has not been fixed in rev#81242. The Error List tool will also now show file and position information regarding a parse error/warning.

Attachments for problem report #15574