Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: DJ Delorie <dj@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Another RFC: regex in libiberty
Date: Fri, 08 Jun 2001 01:15:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20010608095444.01b7aa40@ics.u-strasbg.fr> (raw)
In-Reply-To: <200106080127.VAA01308@greed.delorie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

At 03:27 08/06/01 , vous avez écrit:

>[More lists added to get a wider audience]
>
>I didn't get a clear feeling about what people wanted wrt this.  I saw
>three people propose three versions of regex, not much to go on.  Is
>this a big deal?  Will it really get used by everyone who currently
>has their own regex?  Is it important to try to use a BSD-licensed
>regex to minimize future problems?


  I would really like to get a clearer understanding of this file.
This file is so full of #ifdef that I never really understood much of it.

   Neverthelees, I once sent a patch (without really expecting that it 
would be accepted)
to allow case insensitive expression parsing which is
included in my patch to the gdb-5.0 version for
support of pascal language.

   See
http://sources.redhat.com/ml/gdb/2000-06/msg00146.html
And also Mark Kettenis answers
http://sources.redhat.com/ml/gdb/2000-06/msg00150.html
and
http://sources.redhat.com/ml/gdb/2000-06/msg00155.html

   No decision to change to POSIX entry points were made since
(unless I missed something, which is of course highly possible)



Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99


  parent reply	other threads:[~2001-06-08  1:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Daniel>
     [not found] ` <Vogel's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <Mon,>
     [not found]         ` <01>
     [not found]           ` <Nov>
     [not found]             ` <1999>
     [not found]               ` <14:25:01>
     [not found]                 ` <+0100>
     [not found]                   ` <381D94AD.B37EC167@grafzahl.de>
1999-11-08  8:54                     ` go32-nat.c compilation problem Pierre Muller
     [not found]       ` <Fri,>
     [not found]         ` <08>
     [not found]           ` <Jun>
     [not found]             ` <2001>
     [not found]               ` <10:06:51>
     [not found]                 ` <+0300>
2001-06-07 18:27                   ` Another RFC: regex in libiberty DJ Delorie
2001-06-07 18:31                     ` Ian Lance Taylor
2001-06-07 18:33                       ` DJ Delorie
2001-06-07 18:43                         ` Ian Lance Taylor
2001-06-08  0:11                     ` Eli Zaretskii
2001-06-08  9:18                       ` Mark Mitchell
2001-06-08  9:59                       ` Zack Weinberg
2001-06-08 10:05                         ` H . J . Lu
2001-06-08 10:31                           ` Eli Zaretskii
2001-06-08 10:39                             ` H . J . Lu
2001-06-08 10:37                         ` Eli Zaretskii
2001-06-11 22:49                       ` Jim Blandy
2001-06-11 23:51                         ` Randall R Schulz
2001-06-12  6:48                         ` Jim Blandy
2001-06-08  1:15                     ` Pierre Muller [this message]
2001-06-08  1:36                       ` About struct bpp_transfer_params ±èµæÁß
2001-06-08  7:43                         ` Fernando Nasser
2001-06-09 13:34                     ` Another RFC: regex in libiberty Andrew Cagney
     [not found] <Eli>

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=4.2.0.58.20010608095444.01b7aa40@ics.u-strasbg.fr \
    --to=muller@cerbere.u-strasbg.fr \
    --cc=dj@redhat.com \
    --cc=gdb@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