From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
pluto@agmk.net, gdb@sourceware.org
Subject: Re: overloading 'print' command.
Date: Fri, 15 May 2009 15:53:00 -0000 [thread overview]
Message-ID: <20090515155344.GC17566@adacore.com> (raw)
In-Reply-To: <83k54iqvgk.fsf@gnu.org>
> > I don't see how hook-print can help OP to do something special for
> > std::string. The manual says hook-print doesn't get any arguments, so
> > it can't even tell what is being printed. What am I missing?
>
> Looks like I was missing something: the fact that hooks don't have
> access to the arguments of the hooked command. Sounds like a bad
> limitation to me.
I think that the hooks mechanism is quickly going to be overtaken
by python support, so I personally wouldn't spend any more time
on improving the hooks - especially when the feature is already
available in today's FSF sources.
--
Joel
prev parent reply other threads:[~2009-05-15 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 11:46 Paweł Sikora
2009-05-14 23:17 ` Paul Pluzhnikov
2009-05-15 7:06 ` Eli Zaretskii
2009-05-15 14:07 ` Paul Pluzhnikov
2009-05-15 14:42 ` Eli Zaretskii
2009-05-15 15:53 ` Joel Brobecker [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=20090515155344.GC17566@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=pluto@agmk.net \
--cc=ppluzhnikov@google.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