From: muller@cerbere.u-strasbg.fr
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb@sourceware.cygnus.com
Subject: Re: [RFC] Pascal language: case insensitivity!
Date: Mon, 19 Jun 2000 13:25:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20000619222954.0087c9a0@ics.u-strasbg.fr> (raw)
In-Reply-To: <200006191653.SAA03393@landau.wins.uva.nl>
At 18:53 19/06/00 +0200, Mark Kettenis wrote:
> Date: Mon, 19 Jun 2000 12:51:56 +0200
> From: Pierre Muller <muller@cerbere.u-strasbg.fr>
>
> I already talked a while ago about this and someone (can't remember who)
> said that there is a much simpler way to get this result.
> I would of course really like to know more about this possibility.
>
>It might have been me. I believe I suggested to change GDB to use the
>POSIX entry points regcomp() and regexec() instead of the BSD
>re_comp() and re_exec() functions. There is already a REG_ICASE flag
>that's supposed to ignore case when matching. It's just that you
>cannot use it with re_comp() and re_exec().
>
>The GNU regex library is used by several GNU packages, and the master
>version lives in the GNU C Library. The version in GDB shouldn't
>diverge too much from the master version, and I'm pretty sure your
>patch will be rejected by the maintainer of the GNU C Library.
I don't really care about acceptation of this patch,
but I do care about GDB supporting case insensitivness for pascal language.
So there are two possibilities to consider at least:
- apply my patches only locally in GDB tree.
- use POSIX regex instead of GNU regex in GDB.
I really have no idea about the second issue,
but there might be several drawbacks,
there are probably build systems that don't have
a without POSIX library.
next prev parent reply other threads:[~2000-06-19 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 3:57 Pierre Muller
[not found] ` <200006191653.SAA03393@landau.wins.uva.nl>
2000-06-19 13:25 ` muller [this message]
2000-06-19 15:34 ` Mark Kettenis
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=3.0.6.32.20000619222954.0087c9a0@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=gdb@sourceware.cygnus.com \
--cc=kettenis@wins.uva.nl \
/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