This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: Move symfile.c:generic_load()? Was: RFA: patch to remote.c for larger download packet support (part 1)
- To: cagney at cygnus dot com
- Subject: Re: Move symfile.c:generic_load()? Was: RFA: patch to remote.c for larger download packet support (part 1)
- From: Stan Shebs <shebs at cygnus dot com>
- Date: Thu, 14 Oct 1999 08:10:13 -0700
- CC: gdb-patches at sourceware dot cygnus dot com, fche at cygnus dot com
Date: Thu, 14 Oct 1999 17:31:41 +1000
From: Andrew Cagney <ac131313@cygnus.com>
Before I start on that patch (generic_load needs serious surgery) I'm
wondering if the entire function hould simply be moved to remote.c or
target.c, remote-load.c, generic-load.c, remote-utils.c?
I contemplated this once upon a time, and decided to leave it where it
is. It's certainly not appropriate for remote.c because it's used
with many different protocols, remote-utils.c is a bunch of old junk
that ought to be deleted, target.c is really for target vector
manipulation, not random code. generic_load is nearly unique in that
it is a file-manipulating function that does not use symbolic info,
but it's just one function and not even that complicated, so why
bother to create a new file just for it?
Stan