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]

[Bug libstdc++/17632] Non-portable whitespace in libstdc++ headers


------- Additional Comments From reichelt at gcc dot gnu dot org  2004-09-23 15:00 -------
> Should we not instead ask people to fix their tools to be standard
> compliant, and close this bug as INVALID?  I would consider this a
> bug in whatever tool crashes on this, not one in libstdc++.

Nitpick: It wasn't submitted as a bug, but as an enhancement request.

Even it's a bug in other tools, it would not be a big problem on GCC's
side to make it work. (We are just talking about some whitespace here).
That does not keep us from asking people to fix their tools.

In addition, applying the patch would unify our coding style since we
already have the form "#  include" in our libstdc++ sources.

Therefore, I'd be in favor for applying the patch.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17632


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