This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] ObjC Testsuite
- From: richard at tiptree dot demon dot co dot uk
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: fedor at gnu dot org,fnasser at redhat dot com,msalter at redhat dot com,ezannoni at redhat dot com,gdb-patches at sources dot redhat dot com,Michael Elizabeth Chastain <mec at shout dot net>
- Date: Wed, 5 Mar 2003 06:15:18 +0000
- Subject: Re: [RFA] ObjC Testsuite
On Tuesday, March 4, 2003, at 02:54 pm, Andrew Cagney wrote:
I was getting increasingly worried that, while stuff is being
reviewed, none
of it actually seems to be getting into CVS ... even one of the
earliest patches
to simply add the existing objc code into the configure/make process
and
activate it (which I think one reviewer said was a no-brainer or
something
similar) is still outstanding.
Just FYI, enabling the code for the default build is one of the last
things to happen, not one of the first.
Thanks for the explanation, but I don't find it wholly compelling ...
- gdb's language code isn't modula
There isn't a clean way of dropping in new languages (like many
things, a developer got half way through the process, and then
stopped. It has then remained in that state for ~10 years. A
--with-languages=... isn't there.
I understand that, yet it is the case that most of the objective-c code
has no effect except when debugging an objective-c program, so errors
which were not caught by the review process would only effect
objective-c developers, and frankly, for them it's probably better in
the CVS version of gdb to have partial/unreliable objective-c support
than no support at all. The patch I was referring to (Jan 3rd,
'Compile objc-lang.c objc-exp-tab.c') would seem to be safe.
I would have thought that the *main* point of the review process was to
ensure that any added code did not break existing code, so I assume
that the
objective-c support files in CVS at present are 'safe' (when enabled
they certainly don't seem to break things and I don't see why they
should), and
having patches in place in CVS as rapidly as possible would seem to
make it easier to review later patches ... but you may have found
different in practice.
- this specific code came from [very old] a fork.
As such it needs sigificant work before it gets integrated into GDB.
Adam has been doing a briliant job. What's in GDB is noticably
different to what was in Apple's fork.
Yes ... I did not intend to criticise/complain about Adams work ... I
was just offering to help any way I can, and trying to encourage an
efficient way of getting the work he's done into CVS quickly so he
doesn't have to do yet more work modifying his patches to cope with
changes in gdb.
Anyway, please don't feel compelled to waste time responding to this
... unless you have a suggestion for something I can do to help of
course.