Re: messaging

2009-04-22 Thread Ian Lance Taylor
Arthur Schwarz writes: > In the following code fragment: > > # include > # include > # include > > using namespace std; > void CommandLine(int argc, char** argv); > int main(int argc, char** argv) { >CommandLine(argc, argv[]); >ifstream x.open(argv[1], ios:in); >ofstream y.open(arg

Re: messaging

2009-04-14 Thread Manuel López-Ibáñez
2009/4/14 Arthur Schwarz : > > And there are competitive compilers. Some with better messaging and better > messaging resources at the very point where g++ is weakest. You might argue > that they are 'better in what way?', but I think the real argument is in what > ways can these other products

Re: messaging

2009-04-14 Thread Arthur Schwarz
The issues grow ever more complex. Suppose that we're dealing with macro's, some similarly named, and there's a typo. Suppose several layers of template expansion are involved and nested deep within one there is some error. Suppose, suppose ... . The motivation is not to expand the problem do

Re: messaging

2009-04-14 Thread Jonathan Wakely
2009/4/14 Kai Henningsen: > aschwarz1...@verizon.net schrieb: >> >> Thanks Kai. I do have what I hope is a more specific subjective reason for >> saying that I think the existing diagnostics should be changed. >> Fundamentally, what is provided in the messaging is not an indication of >> what is wr

Re: messaging

2009-04-14 Thread James Dennett
On Tue, Apr 14, 2009 at 9:21 AM, wrote: > > Thanks Kai. I do have what I hope is a more specific subjective reason for > saying that I think the existing diagnostics should be changed. > Fundamentally, what is provided in the messaging is not an indication of what > is wrong, but an indication

Re: messaging

2009-04-14 Thread Kai Henningsen
aschwarz1...@verizon.net schrieb: Thanks Kai. I do have what I hope is a more specific subjective reason for saying that I think the existing diagnostics should be changed. Fundamentally, what is provided in the messaging is not an indication of what is wrong, but an indication of what is requ

Re: messaging

2009-04-14 Thread aschwarz1309
rch goes the way of the woolly-mammoth. The paradigm is that the message should provide the minimum amount of information required to identify the syntax/semantics which caused the failure. art --- On Mon, 4/13/09, Kai Henningsen wrote: > From: Kai Henningsen > Subject: Re: messaging

Re: messaging

2009-04-13 Thread Kai Henningsen
Arthur Schwarz schrieb: In the following code fragment: # include # include # include using namespace std; void CommandLine(int argc, char** argv); int main(int argc, char** argv) { CommandLine(argc, argv[]); ifstream x.open(argv[1], ios:in); ofstream y.open(argv[1], ios::in);