From: Simon Marchi <simon.marchi@polymtl.ca>
To: George Barrett <bob@bob131.so>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] guile: fix smob exports
Date: Mon, 9 Aug 2021 23:21:43 -0400 [thread overview]
Message-ID: <079cac55-8e1a-13ed-6159-2203c2bf9085@polymtl.ca> (raw)
In-Reply-To: <zq2o&y6&9rnbpkh218eagmr3u&ksm4hr/atbia-fxs7t8wfom0mx@mail.bob131.so>
On 2021-08-09 11:04 p.m., George Barrett wrote:
> On Tue, Aug 10, 2021 at 11:02:00 +1000, Simon Marchi wrote:
>> I didn't understand though from your explanation what consequence the
>> bad behavior has. What did it prevent a Guile user to do?
>
> Ah, sorry. There is a range of cases in which it's necessary or
> convenient to be able to refer to a GDB smob type, for instance:
> - Pattern matching based on the type of a value.
> - Defining GOOPS methods handling values from GDB (GOOPS methods
> typically use dynamic dispatch based on the types of the arguments).
> - Type-checking assertions when applying some defensive programming on
> an interface.
> - Generally any other situation one might encounter in a dynamically
> typed language that might need some introspection.
>
> If you're more familiar with Python, it would be quite similar to being
> unable to refer to the classes exported from the GDB module (which is to
> say: not crippling for the most part, but makes certain tasks more
> difficult than necessary).
>
> Should I resubmit the patch with something like the above explanation
> included in the commit message?
>
>> I'm fine with you merging the patch.
>
> Great! Assuming the answer to the above question is 'no', would you mind
> pushing it on my behalf?
Thanks a lot, done with the extra explanation you gave above added to
the commit message.
Simon
prev parent reply other threads:[~2021-08-10 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 18:49 George Barrett
2021-07-28 23:23 ` [PING] " George Barrett
2021-08-09 22:19 ` [PING**2] " George Barrett
2021-08-10 1:02 ` Simon Marchi
2021-08-10 3:04 ` George Barrett
2021-08-10 3:21 ` Simon Marchi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=079cac55-8e1a-13ed-6159-2203c2bf9085@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=bob@bob131.so \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).