http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31983
Manuel López-Ibáñez manu at gcc dot gnu.org changed:
What|Removed |Added
CC||manu at gcc
--- Comment #12 from pinskia at gcc dot gnu dot org 2008-12-24 23:14
---
This is not useful as sometimes it is hard to point out the one C99/C++98 which
tells you why your code is invalid, in some cases you need to point to 3
different locations in the standard and read that. An
--- Comment #11 from esigra at gmail dot com 2008-09-21 20:38 ---
I found that James' wish is already implemented in some cases:
$ strings /usr/i686-pc-linux-gnu/gnat-gcc-bin/4.2/gnat|grep RM
illegal use of remote access-to-class-wide type, see RM E.4(18)
A user that gets that error
--- Comment #10 from pinskia at gcc dot gnu dot org 2008-09-03 02:42
---
for warnings, we do provide (in most cases) the option that enables/disables
the warning. But I don't see this happening any time soon, if ever.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31983
--- Comment #9 from manu at gcc dot gnu dot org 2008-05-08 10:44 ---
(In reply to comment #8)
Sorry, you got it totally wrong! When someone suggests a feature that he
thinks
would be useful, he does definitely not imply that the current developers are
bored and have nothing to
--- Comment #7 from manu at gcc dot gnu dot org 2008-05-07 10:06 ---
(In reply to comment #6)
Colorization of a message is part of the message. It should obviously be done
whereever the message is constructed. (IDE has nothing to do with this.) With
your argument, the compiler should
--- Comment #8 from esigra at gmail dot com 2008-05-07 13:08 ---
(In reply to comment #7)
Adding color output (ala ls --color) or the proposal in this bug (gcc as a
lecturer in programming) show a critical misunderstanding: Assuming that GCC
developers are bored and have nothing to
--- Comment #4 from esigra at gmail dot com 2008-05-06 18:00 ---
(In reply to comment #3)
2) Standards are not freely distributable, thus they are not widely available.
You say that as if it was a general fact, but it is certainly not. For example
the Ada reference manual is available
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-05-06 18:21 ---
But seriously colorization should not be done in the compiler. Just like IDE
should not be part of the compiler ...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31983
--- Comment #6 from esigra at gmail dot com 2008-05-06 18:47 ---
(In reply to comment #5)
But seriously colorization should not be done in the compiler. Just like IDE
should not be part of the compiler ...
Colorization of a message is part of the message. It should obviously be done
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31983
--- Comment #3 from manu at gcc dot gnu dot org 2007-05-18 14:16 ---
I see several reasons for not doing this:
1) External tools expect the current output format. Your proposal will break
that.
2) Standards are not freely distributable, thus they are not widely available.
3) Getting
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-18 01:13 ---
Alternatively, or in combination, gcc could provide references to more
widely-available sources (such as KR and HS for C, and Stroustrup or the ARM
for C++ for example).
Except those are very unofficial when it
--- Comment #2 from fang at csl dot cornell dot edu 2007-05-18 03:27
---
wishfulthinking
It's too bad the holy standard documents (ISO/IEC) aren't free or freely
distributable, they could be nice supplementary reference material to go along
with a compiler, even one that isn't
14 matches
Mail list logo
