From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Simplify MI breakpoint setting
Date: Mon, 31 Aug 2009 23:35:00 -0000 [thread overview]
Message-ID: <m3eiqry3ee.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200908241353.40486.vladimir@codesourcery.com> (Vladimir Prus's message of "Mon, 24 Aug 2009 13:53:40 +0400")
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Volodya> And, progressing recursively, what is the point of not exposing
Volodya> all the parameters of break_command_really?
I don't actually know. But if I had to guess, I would say it is because
providing wrappers ensures you can't pass in some forms of nonsense.
If you really want to do it, and nobody objects, then I guess I don't
care all that much. This whole API seems a bit nuts, any time you have
13 arguments you should just assume you've done something wrong already.
I do care about not exporting a function named "break_command_really"
though.
Tom
next prev parent reply other threads:[~2009-08-31 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 7:13 Vladimir Prus
2009-08-07 18:52 ` Tom Tromey
2009-08-24 10:55 ` Vladimir Prus
2009-08-31 23:35 ` Tom Tromey [this message]
2009-09-01 5:16 ` Vladimir Prus
2009-09-07 23:00 ` Matt Rice
2009-09-08 5:20 ` Vladimir Prus
2009-09-08 7:59 ` Matt Rice
2009-09-08 8:15 ` Vladimir Prus
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=m3eiqry3ee.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.com \
/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