From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] pascal: Add lowercase copy of symbol name
Date: Thu, 29 Apr 2010 22:54:00 -0000 [thread overview]
Message-ID: <002a01cae7ee$e144b6d0$a3ce2470$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100429223157.GA2768@adacore.com>
> I can't really say that I am fond of this approach - at all. We already
> store the linkage name as well as the natural name. Can't you use that
> in the language-specific lookup routines to make the search case
> insensitive?
The problem is that if we want to keep the true case
of the symbols (which I at least want), doing case-insensitive
searching required practically to lowercase on the fly
all pascal symbol each time an expression is evaluated.
This is very inefficient.
> There is also something I'm confused about: If Pascal is *not* case-
> sensitive, why make the debugger optionally case-sensitive? Why not
> always have a case-insensitive interpreter? You aluded that there were
> some reasons...
There are some internal functions or variables inside Free Pascal
that are lowercase to avoid possible conflict with
explicitly declared functions or variables (who are completely
UPPERCASED in Free Pascal).
GNU pascal uses First Letter Capitalization for its
declared function/variables (I don't know the internals of GPC).
In the printout, I would like to keep this difference
between internal and declared variables.
If I have an internal variable named stdout,
and a declared variable STDOUT.
I would really prefer to still be able to
only get one matching variable if I use the exact matching
stdout or STDOUT.
Pierre Muller
Pascal language support maintainer for GDB
next prev parent reply other threads:[~2010-04-29 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 22:18 Pierre Muller
2010-04-29 22:32 ` Joel Brobecker
2010-04-29 22:54 ` Pierre Muller [this message]
2010-04-29 23:09 ` Joel Brobecker
2010-04-30 7:27 ` Jan Kratochvil
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='002a01cae7ee$e144b6d0$a3ce2470$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.com \
--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