From: David Ayers <d.ayers@inode.at>
To: Daniel Jacobowitz <drow@false.org>
Cc: Thomas Richter <thor@mail.math.tu-berlin.de>,
gdb-patches@sourceware.org
Subject: Re: C++ support improvement patch
Date: Mon, 23 Jan 2006 14:57:00 -0000 [thread overview]
Message-ID: <43D4EEA7.1080303@inode.at> (raw)
In-Reply-To: <20060123141344.GA13883@nevyn.them.org>
Daniel Jacobowitz schrieb:
>>o) For TAB-expansion, it removes the ":" as word-delimiter for
>>readline, thus allowing to find names in namespaces. The current
>>behaivour here is completely unusable for C++. The patch could
>>be better, though, it should read template argument delimiters < >
>>and function argument delimiters ( ) as "quotation characters",
>>though it doesn't. Though it's a huge improvement compared to
>>previous versions where TAB expansion was just not usable for C++.
>
>
> This isn't the right fix, though. Someone posted (Pierre Muller, a
> long time ago - April 2002!) an initial patch to make tab completion
> context sensitive (for Pascal) - tab complete to the colon, type the
> colon, and then tab complete structure members after the colon.
>
> It isn't suitable as-is and no one ever had time to go back and improve
> it but that's what ought to be done.
>
I also would be very interested in this part of an acceptable patch as
to possibly take a shot at fixing tab completion for Objective-C methods.
/me searches the archives
I think you mean:
http://sources.redhat.com/ml/gdb-patches/2002-04/msg00774.html
It would also be interesting to know if Apple has an acceptable proposal
for this especially in light of Objective-C++.
Cheers,
David
next prev parent reply other threads:[~2006-01-23 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 9:50 Thomas Richter
2006-01-23 14:13 ` Daniel Jacobowitz
2006-01-23 14:57 ` David Ayers [this message]
2006-01-23 15:00 ` Thomas Richter
2006-01-23 15:05 ` Daniel Jacobowitz
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=43D4EEA7.1080303@inode.at \
--to=d.ayers@inode.at \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=thor@mail.math.tu-berlin.de \
/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