This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB 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: [commit] cleanup stale exec.{h|c} xfer_memory comments.

From: Joel Brobecker <brobecker at adacore dot com>
To: Tom Tromey <tromey at redhat dot com>
Cc: Eli Zaretskii <eliz at gnu dot org>, Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org
Date: Mon, 15 Jun 2009 17:19:53 -0700
Subject: Re: [commit] cleanup stale exec.{h|c} xfer_memory comments.
References: <200906121943.08246.pedro@codesourcery.com> <E1MFKCv-000806-VP@fencepost.gnu.org> <20090613111210.GN25703@adacore.com> <m3fxe15p1c.fsf@fleche.redhat.com>

> FWIW, I prefer to have documentation in the header for a module's
> public API, and next to the implementation for the private API.
> Consistency doesn't matter as much to me as being able to read a
> header file and get a grasp of how I would use a module; the private
> comments in the module can then describe the implementation.

I would be OK with this approach too.

-- 
Joel

References:
- [commit] cleanup stale exec.{h|c} xfer_memory comments.
  - From: Pedro Alves
- Re: [commit] cleanup stale exec.{h|c} xfer_memory comments.
  - From: Eli Zaretskii
- Re: [commit] cleanup stale exec.{h|c} xfer_memory comments.
  - From: Joel Brobecker
- Re: [commit] cleanup stale exec.{h|c} xfer_memory comments.
  - From: Tom Tromey

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