This is the mail archive of the gcc-patches@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: [v3] Undo 2001-11-30 libsupc++ changes

From: Jason Merrill <jason at redhat dot com>
To: Paolo Carlini <pcarlini at unitus dot it>
Cc: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Wed, 09 Jan 2002 23:11:13 +0000
Subject: Re: [v3] Undo 2001-11-30 libsupc++ changes
References: <3C3CAB67.70B0D2BB@unitus.it><wvlu1tvi1fn.fsf@prospero.cambridge.redhat.com><3C3CC9AB.617D7AF9@unitus.it>

>>>>> "Paolo" == Paolo Carlini <pcarlini@unitus.it> writes:

> Ah! I did'nt understand that he meant *in the code* (vs, in the ChangeLog)

I believe very strongly that comments belong in code.  If I'm mucking about
in the source, I shouldn't have to look elsewhere for rationale.  If it's
not where I'm already looking, chances are very good that I won't see it.
Commentary in the ChangeLog should be limited to describing what a large
batch of changes does, not why it is a good idea.

Jason

Follow-Ups:
- Re: [v3] Undo 2001-11-30 libsupc++ changes
  - From: Paolo Carlini

References:
- [v3] Undo 2001-11-30 libsupc++ changes
  - From: Paolo Carlini
- Re: [v3] Undo 2001-11-30 libsupc++ changes
  - From: Jason Merrill
- Re: [v3] Undo 2001-11-30 libsupc++ changes
  - From: Paolo Carlini

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