• Christian Kaiser (34/34) Oct 05 2003 A nice feature of Watcom is that it shows the "path" where an error is
• Walter (3/6) Oct 05 2003 Sorry, there isn't.

"Christian Kaiser" <chk online.de> writes:

A nice feature of Watcom is that it shows the "path" where an error is
coming from; say for

 int f(int n)
 {
  return(1);
 }
 char f(int n)
 {
  return(1);
 }

Watcom says:


    x.c(13): Error! E385: col(9) attempt to overload function 'f' with a
different return type
    x.c(13): Note! N392: col(9) 'int f( int )' defined in: x.c(8) (col 13)

and DMC:

            {
            ^
    x.c(13) : Error: 'f' previously declared as something else
    It was declared as: int C func(int )
    It is now declared: char C func(int )
             return(1);
                  ^
    x.c(14) : Error: '=', ';' or ',' expected
            }
            ^

    x.c(15) : Error: identifier or '( declarator )' expected


MS is the laziest, simply telling


    x.c(13) : error C2556: 'f' : overloaded functions only differ by return
type


Is there a command line switch to get that invaluable information where a
previous definition is from, and possibly how it's included (this c file
included the header file x, which ...)?


Thanks,
Christian

"Walter" <walter digitalmars.com> writes:

"Christian Kaiser" <chk online.de> wrote in message
news:blomb6$6od$1 digitaldaemon.com...
 Is there a command line switch to get that invaluable information where a
 previous definition is from, and possibly how it's included (this c file
 included the header file x, which ...)?

Sorry, there isn't.