From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: MinGW port
Date: Tue, 05 Sep 2006 09:11:08 +1000 [thread overview]
Message-ID: <87slj7kz1v.fsf@zip.com.au> (raw)
In-Reply-To: <87lkoz8ea5.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 04 Sep 2006 23:20:34 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> do you understand exactly what the
> Win32/MinGW compiler is complaining about?
The function takes "const char * const *" but the actual parameter is
"char **".
I've never understood why that should provoke a complaint. Const is a
promise by the func that it won't modify the contents (of either the
array or the contained strings) so surely it's acceptable to pass
something that is allowed to be modified, isn't it?
In any case, __MINGW32__ conditionals are pretty horrible, I'd much
prefer to see guile not force "-Werror" on unsuspecting users. Or not
do it on mingw at least.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-09-04 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 16:42 MinGW port Nils Durner
2006-09-04 22:20 ` Neil Jerram
2006-09-04 23:11 ` Kevin Ryde [this message]
2006-09-06 1:23 ` Rob Browning
2006-09-09 18:14 ` Nils Durner
2006-09-12 0:56 ` Ken Raeburn
2006-09-14 0:21 ` Kevin Ryde
2006-09-25 17:54 ` Nils Durner
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=87slj7kz1v.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).