From: Neil Jerram <neil@ossau.uklinux.net>
To: linasvepstas@gmail.com
Cc: Andy Wingo <wingo@pobox.com>,
guile-user@gnu.org, Peter Brett <peter@peter-b.co.uk>,
guile-devel@gnu.org
Subject: Re: Reconsideration of MinGW work
Date: Tue, 23 Mar 2010 00:20:27 +0000 [thread overview]
Message-ID: <87d3yvlwhg.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <3ae3aa421003221305y1dfbdb41sc2c563dc0432938e@mail.gmail.com> (Linas Vepstas's message of "Mon, 22 Mar 2010 14:05:44 -0600")
Linas Vepstas <linasvepstas@gmail.com> writes:
> My pet peeve with mingw is the lack of ready-to-go regex. This is completely
> unrelated to guile; I have another project that made the mistake of assuming
> that regex "just worked" on windows, and I've been bitched at ever
> since.
Gnulib has a regex library.
> Getting regex into mingw and having it "just work" would be excellent.
But that won't happen, because that's not part of MinGW's mission. All
MinGW is trying to do is provide a free software toolset for building
native Windows programs - which at runtime will link to the standard set
of DLLs that M$ provides. Those DLLs don't provide regex, so the MinGW
header files don't provide regex either.
Neil
next prev parent reply other threads:[~2010-03-23 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 20:51 Reconsideration of MinGW work Neil Jerram
2010-03-21 21:36 ` Grant Rettke
2010-03-22 1:28 ` Ken Raeburn
2010-03-22 20:10 ` Andy Wingo
2010-03-22 23:38 ` Greg Troxel
2010-03-23 0:04 ` Neil Jerram
2010-03-23 6:59 ` Ken Raeburn
2010-03-23 8:50 ` Andy Wingo
2010-03-22 8:10 ` Peter Brett
2010-03-22 20:00 ` Andy Wingo
2010-03-22 20:05 ` Linas Vepstas
2010-03-23 0:20 ` Neil Jerram [this message]
2010-03-23 0:13 ` Neil Jerram
2010-03-28 22:26 ` Ludovic Courtès
2010-03-29 20:34 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3yvlwhg.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=linasvepstas@gmail.com \
--cc=peter@peter-b.co.uk \
--cc=wingo@pobox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).