This is the mail archive of the gdb-patches@sourceware.cygnus.com 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]

Re: gdb.h, libgdb.h, gdblib.h, gdb-lib.h, ...?



   Date: Mon, 13 Dec 1999 11:35:31 +1100
   From: Andrew Cagney <ac131313@cygnus.com>

   So, ok I've been ignoring this one.

   We're going to try to create a library.  Some bits, like ``struct
   gdb_file'' can easily live in ``gdb-file.h'' where they can be (fairly
   safely) included by non-core GDB code.

   But what of the main GDB functions? Eg:

	   XXX {lib,}gdb{,lib}_breakpoint_query (..., b, ...);

   For the moment, based on a detailed probabilistic analysis (coin toss)
   I'll assume ``gdb.h''.  If anyone can think of a compelling case for
   some other name, please speak now :-)

I'd vote for libgdb.h, since a) it's the term we've been using for the
past seven years, and b) it's useful to emphasize that this is a
library interface, not something that is purely internal to GDB.  For
instance, if you look at X11, X clients normally include Xlib.h.
Xlib.h then includes X.h, which is the lower-level stuff that's (at
least partly) common to both clients and servers.

I'd also like us just to have a single .h file that includes
everything that a libgdb client would need.  It's going to be very
hard for someone to use just part of libgdb, because of all the
internal interconnections.  If GDB ever gets decoupled internally,
and anybody cares, they can split libgdb.h too - until then we'd
just be deceiving ourselves.

								Stan



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