rmf@cs.columbia.edu (Robert M. Fuhrer) (02/22/91)
Well, since we're on the subject, the IBM RS/6000 XLC C compiler generates pretty funny looking error messages. The really unfortunate part is that where compilation-error-regexp is expected to parse a file name and line number, the XLC compiler's messages don't include the file name. Does anyone have a solution? I've really gotten used to this feature, and would hate to see it go... -- -------------------------- Robert M. Fuhrer Computer Science Department Columbia University 1117B Fairchild Building Internet: rmf@cs.columbia.edu UUCP: ...!rutgers!cs.columbia.edu!rmf
barmar@think.com (Barry Margolin) (02/23/91)
In article <RMF.91Feb21171911@chopin.cs.columbia.edu> rmf@cs.columbia.edu (Robert M. Fuhrer) writes: >Well, since we're on the subject, the IBM RS/6000 XLC C compiler generates >pretty funny looking error messages. The really unfortunate part is that >where compilation-error-regexp is expected to parse a file name and line >number, the XLC compiler's messages don't include the file name. Does anyone >have a solution? I've really gotten used to this feature, and would hate to >see it go... If the compiler's messages don't include the file name, how do *humans* figure out which file the message refers to? If humans can't do it, then we'd be hard pressed to teach a computer to do it. -- Barry Margolin, Thinking Machines Corp. barmar@think.com {uunet,harvard}!think!barmar
rmf@cs.columbia.edu (Robert M. Fuhrer) (02/27/91)
>In article <RMF.91Feb21171911@chopin.cs.columbia.edu> rmf@cs.columbia.edu (Robert M. Fuhrer) writes: >>Well, since we're on the subject, the IBM RS/6000 XLC C compiler generates >>pretty funny looking error messages. The really unfortunate part is that >>where compilation-error-regexp is expected to parse a file name and line >>number, the XLC compiler's messages don't include the file name. Does anyone >>have a solution? I've really gotten used to this feature, and would hate to >>see it go... > >If the compiler's messages don't include the file name, how do *humans* >figure out which file the message refers to? If humans can't do it, then >we'd be hard pressed to teach a computer to do it. >-- >Barry Margolin, Thinking Machines Corp. Well, of course, the problem is that it doesn't include the file name on each line. I've since realized the way to do it is by pre-processing the compilation buffer to insert the filename on each line so as not to have to munge compilation-parse-errors. -- -------------------------- Robert M. Fuhrer Computer Science Department Columbia University 1117B Fairchild Building Internet: rmf@cs.columbia.edu UUCP: ...!rutgers!cs.columbia.edu!rmf