From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stan Shebs To: toddpw@wrs.com Cc: gdb-patches@cygnus.com Subject: Re: libgdb.a Date: Thu, 01 Apr 1999 00:00:00 -0000 Message-ID: <199903112040.MAA03640@andros.cygnus.com> References: <199903110056.QAA00306@alabama.wrs.com> X-SW-Source: 1999-q1/msg00083.html Message-ID: <19990401000000.jq984exkNCD6T_YZnWl94YtOX6Z0HyQ-8wK4q2RdUck@z> From: toddpw@wrs.com (Todd Whitesel) Date: Wed, 10 Mar 1999 16:56:04 -0800 (PST) I would love it if more things in GDB were "constructored" and not #define'd or hardcoded. Right now (read 4.17) with many remote targets you can't know the exact register list until you probe the target to find out what it is, yet the reg_names[] array is statically initialized (because on ptrace unix platforms that Just Worked), and we're just lucky that the rest of GDB adapts well to having reg_names[] edited after initialization. As I mentioned a couple weeks ago to one of the lists, more dynamic construction is the way to go in the future. One thing that individuals can do now to ease the transition is to avoid ifdefs in their patches. It should be clear to everyone that a GDB littered with target ifdefs is not going to be able to make runtime choices about anything. So, avoid the ifdef! Stan