This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 2/9] Define and export Guile classes for all GDB object types
- From: Doug Evans <xdje42 at gmail dot com>
- To: Andy Wingo <wingo at igalia dot com>
- Cc: gdb-patches at sourceware dot org, ludo at gnu dot org
- Date: Tue, 27 May 2014 00:35:04 -0700
- Subject: Re: [PATCH v2 2/9] Define and export Guile classes for all GDB object types
- Authentication-results: sourceware.org; auth=none
- References: <1397731588-23750-1-git-send-email-wingo at igalia dot com> <1397731588-23750-3-git-send-email-wingo at igalia dot com> <m3vbtvr71l dot fsf at sspiff dot org>
Doug Evans <xdje42@gmail.com> writes:
> Andy Wingo <wingo@igalia.com> writes:
>
>> gdb/ChangeLog:
>> * guile/scm-gsmob.c (gdbscm_make_smob_type): Define a binding
>> for a GOOPS class corresponding to the SMOB type.
>> (gdbscm_initialize_smobs): Load GOOPS.
>>
>> * guile/lib/gdb.scm: Export the GOOPS classes.
>
> No blank line between related changelog entries.
>
> Question: Is it possible to define the goops classes at some
> random future point [e.g., long after gdb has initialized]?
> Some might prefer not bringing goops into the picture unless
> explicitly requested.
I was thinking,
given that the guile 2.0 behaviour is deprecated in guile 2.2,
let's just punt on goops support for the gdb 7.8 release.
There's no rush, and we can revisit after 7.8 goes out.
To that end, I think the thing to do here is remove the scm-generics.exp
testcase, and make sure the manual mentions goops isn't currently
supported.