From: Joel Brobecker <brobecker@gnat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Word break characters are language dependent
Date: Sun, 21 Sep 2003 21:43:00 -0000 [thread overview]
Message-ID: <20030921214323.GE15984@gnat.com> (raw)
In-Reply-To: <1438-Sun21Sep2003152844+0300-eliz@elta.co.il>
> > Unfortunately, the word-break characters for Ada are not exactly the
> > same as the ones used by default. As a consequence, the current
> > completer does not always find the correct starting location of the
> > symbol name. So I think we should make them language-dependent by
> > adding a new field to the language vector.
>
> Did you actually try to replace the hard-coded string with a different
> one that is good for Ada, and see if that solves your problem?
Yes :).
What I actually did while waiting for the opinion of the maintainers
and developpers was to make our Ada version of this string non-static,
and changed gdb_get_completer_word_break_character() return the ada
string if the current_language was ada. I then used that function
in place of the string itself in the one location where I detected
the problem.
> So I think before we discuss the design of a possible solution, we
> should be sure that it is in fact a solution ;-)
Right! :-) That reminds me of a collegue in my previous job that often
came to the chif software architect with grand designs, some of them
almost extravagant. And this architect will always smile while asking
the same question after the presentation: "Are you sure it works?".
And this collegue would smile back and always say the same: "Yes,
because I implemented it" :-).
In this particular case, I didn't actually implement what I am
suggesting. I just did a hack, a prototype if you like, that proves
that it should work well.
> Other than that, I think your general idea is correct and the proposed
> direction is reasonable.
Thanks for your input, it is much appreciated. I'll wait for another
week to see if I can get more feedback, and then will try to work on
a patch.
--
Joel
next prev parent reply other threads:[~2003-09-21 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 19:16 Joel Brobecker
2003-09-21 12:32 ` Eli Zaretskii
2003-09-21 21:43 ` Joel Brobecker [this message]
2003-09-22 5:14 ` Eli Zaretskii
2003-09-23 18:35 ` Joel Brobecker
2003-09-24 5:34 ` Eli Zaretskii
2003-09-24 18:13 ` Joel Brobecker
2003-09-22 7:24 ` Andrew Cagney
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=20030921214323.GE15984@gnat.com \
--to=brobecker@gnat.com \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.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