RFC: gdb/targets

[Fernando Nasser <fnasser at redhat dot com>]

It is annoying to work with the gdb directory with the number of files
that it has today.  Andrew said that, in the future, we will have a
series of subdirectories.

While this does not occur, I was looking for some immediate relief and I
noticed that we have a class with a good number of files with clear
separation that we could separate right now.

As you know, GDB has a core part of the code that talks to several
"targets" that implement operations of the "target vector".  I propose
that we move these files (I volunteer) to a gdb/targets subdirectory
(please see the list of files below).

My only doubt is where we should keep the target.c file itself, or even
the target.h file (which defines the target vector proper).  Should they
go in the subdirectory or stay at the top level GDB directory?

Here is the list of "target implementation files" not including
target.[ch]:

abug-rom.c
corelow.c
cpu32bug-rom.c
dbug-rom.c
dink32-rom.c
dve3900-rom.c
exec.c
gnu-nat.c
go32-nat.c
hpux-thread.c
inftarg.c
lin-lwp.c
lin-thread.c
linux-thread.c
m32r-rom.c
m3-nat.c
mac-nat.c
mcore-rom.c
mon960-rom.c
monitor.c
ocd.c
op50-rom.c
ppc-bdm.c
ppcbug-rom.c
procfs.c
remote-adapt.c
remote-array.c
remote-bug.c
remote.c
remote-e7000.c
remote-eb.c
remote-es.c
remote-est.c
remote-hms.c
remote-mips.c
remote-mm.c
remote-nindy.c
remote-nrom.c
remote-os9k.c
remote-rdi.c
remote-rdp.c
remote-sds.c
remote-sim.c
remote-st.c
remote-udi.c
remote-vx.c
rom68k-rom.c
sh3-rom.c
sol-thread.c
sparclet-rom.c
sparcl-tdep.c
thread-db.c
uw-thread.c
v850ice.c
w89k-rom.c
win32-nat.c
wince.c


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9