|Bill Allombert on Tue, 15 Sep 2009 19:08:35 +0200|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|Re: Improving warning output|
On Tue, Sep 15, 2009 at 11:28:08AM -0400, Igor Schein wrote: > Hi, > > This is an example I'll be talking about: > > ? thue(thueinit(x^7-401),88); > *** thue: Warning: Non trivial conditional class group. > *** The result returned by 'thue' is conditional on the GRH. For that particular instance, the interface is wrong: whether the result is conditional or not should be part of the output (or the input), not printed to the screen. > 1) To improve grep-ability of the output, I would strongly consider > including the tag "Warning" in all warning lines, not just the first one, if > they *must* be split. In this particular example, I would think they can be > squeezed into 1 line, though I would like a confirmation from the core > PARI/GP developers. If user need to grep for warning, I think we have already lost. > 2) If the same output file contains another warning line, say " *** bnfinit: > Warning: insufficient precision for fundamental units, not given.", then > warning tags wouldn't be aligned vertically, because of length difference > between words thue and bnfinit. I would tentatively consider putting tag > "Warning" before the function name, to improve visual presentation. The current state of affair is a side effect of a change to add function name before error message, not something that was really intended. Cheers, Bill.