This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: code that could be improved


"Joseph S. Myers" <jsm@polyomino.org.uk> writes:

| On Tue, 2 Mar 2004, Roland Illig wrote:
| 
| > I'm currently translating gcc-3.4-b20040206 into German. Here is a list
| > of things I don't like in the current code:
| 
| Please report each issue as a separate bug to our bug database so that
| they can be tracked.  <http://gcc.gnu.org/bugs.html>, as referenced in the
| Report-Msgid-Bugs-To line of gcc.pot, makes clear this is preferred.
| 
| > - various quoting techniques: `foo', 'bar', "baz".
| >    => please use `foo' consistently
| 
| Why that form?  'foo' is more correct for plain ASCII, unless and until we

Each time I've expressed that form, people have made the characterization
that I was being dense.  I suppose that if *you* make it, it would be more
acceptable <g>. 

Anyway,  actually, I think we need something more than just 'foo' for
proper handling in the pretty-printer.  There is at least one PR open
since ages that is better handled by such a clear qoute marker
understood by the pretty-printer (e.g. %"foo, %'foo, %whateverfoo).
The reason is that the line-wrapper needs to have a clear knowledge of
when it is in the middle of (or just starting a quote) so that it
"cuts" properly. 

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]