From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: dje@google.com (Doug Evans)
Cc: drow@false.org (Daniel Jacobowitz), gdb-patches@sourceware.org
Subject: Re: Per-type architecture (Re: [10/15] Basic value access routines)
Date: Tue, 23 Jun 2009 16:57:00 -0000 [thread overview]
Message-ID: <200906231657.n5NGv9ON014293@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <e394668d0906230855g86466bcj62893515407641be@mail.gmail.com> from "Doug Evans" at Jun 23, 2009 08:55:39 AM
Doug Evans wrote:
> On Mon, Jun 22, 2009 at 5:41 PM, Ulrich Weigand<uweigand@de.ibm.com> wrote:
> > In fact, if it weren't that
> > we want to avoid excessive dependencies on XML libraries, I'd argue we should
> > just parse XML into a standard DOM tree representation as provided by those.
> >
> > Looking at this this way, serialization/deserialization of XML into and out
> > of those "DOM tree" structures *should not* involve too much GDB specifics
> > like GDB private data structures, but simply follow the self-describing
> > property of the XML format ...
>
> OOC, what "excessive dependencies" are you referring to?
> It seems odd to want to avoid dependencies on libraries, libraries are good.
> [I'm sure there's more to the story here, hence the question. :-)]
Well, the concern was in fact really about adding a dependency on an external
library, if I recall correctly. GDB always used to be pretty self-contained,
you don't need to install any external libraries in order to build or use it.
While libraries are good from a developer's point of view, dependencies add
hassles for users ...
Daniel initially suggested to add the expat sources to the src tree in order
to keep that property, see the original discussion here:
http://sourceware.org/ml/gdb-patches/2006-07/msg00231.html
This approach was then discarded in favor of using an external expat library
installed by the user, but only for "non-essential" purposes: if that library
does not exist, it must still be possible to build and use GDB even if some
non-essential GDB features then no longer work:
http://sourceware.org/ml/gdb-patches/2006-08/msg00048.html
That's what I meant by "excessive dependency": if we were to add library
calls to core GDB components with no fallback option, this would *require*
presence of the library, or else GDB will not build at all any more. Up
to now we've always said we don't want to do that.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-06-23 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:20 [10/15] Basic value access routines Ulrich Weigand
2009-06-15 16:35 ` Doug Evans
2009-06-15 16:59 ` Ulrich Weigand
2009-06-22 20:32 ` Per-type architecture (Re: [10/15] Basic value access routines) Ulrich Weigand
2009-06-22 20:59 ` Daniel Jacobowitz
2009-06-23 0:41 ` Ulrich Weigand
2009-06-23 13:49 ` Daniel Jacobowitz
2009-06-23 14:02 ` Pedro Alves
2009-06-23 17:06 ` Ulrich Weigand
2009-06-23 17:30 ` Daniel Jacobowitz
2009-06-23 15:55 ` Doug Evans
2009-06-23 16:42 ` Mark Kettenis
2009-06-23 16:53 ` Daniel Jacobowitz
2009-06-23 16:57 ` Ulrich Weigand [this message]
2009-06-23 17:36 ` Doug Evans
2009-06-24 15:31 ` [10/15] Basic value access routines Tom Tromey
2009-06-24 15:46 ` Daniel Jacobowitz
2009-06-24 16:26 ` Doug Evans
2009-06-24 19:41 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906231657.n5NGv9ON014293@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=dje@google.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox