From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: i686-w64-mingw32-gcc: LC_MESSAGES
Date: Wed, 09 Jan 2019 18:14:00 -0000 [thread overview]
Message-ID: <CAD8GWsv60NNtaAy_4rDfKUDGMEC4UgfiOMZFzAVng2908KPaFg@mail.gmail.com> (raw)
In-Reply-To: <92c7e8c2-c440-1bb8-f329-23951d10dffe@gmail.com>
On 1/9/19, JonY wrote:
> On 1/8/19 9:26 PM, Lee wrote:
>> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/locale.h.html
>> has a note for LC_MESSAGES:
>> The functionality described is an extension to the ISO C standard.
>> Application developers may make use of an extension as it is
>> supported on all POSIX.1-2017-conforming systems.
>>
>> i686-w64-mingw32-gcc doesn't have LC_MESSAGES defined.
>> Is that an oversight, something missing in windows, or .. ??
>>
>
> Windows MSVCR isn't POSIX nor ISO C compliant, so you shouldn't be
> referring to opengroups, only against MSDN.
What's a Windows MSVCR?
Since the same program compiled with cygwins' gcc has LC_MESSAGES
defined, I was guessing it was just a library thing and maybe it just
hadn't been implemented in the mingw libraries yet.. but it sounds
like it's not an oversight & Microsoft needs to support LC_MESSAGES
before i686-w64-mingw32-gcc will. Is that about right?
Thanks,
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-01-09 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 21:26 Lee
2019-01-09 10:21 ` JonY
2019-01-09 18:14 ` Lee [this message]
2019-01-09 18:19 ` Douglas Coup
2019-01-09 19:43 ` Lee
2019-01-09 23:41 ` Brian Inglis
2019-01-10 0:07 ` Lee
2019-01-09 23:43 ` JonY
2019-01-10 0:51 ` Lee
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=CAD8GWsv60NNtaAy_4rDfKUDGMEC4UgfiOMZFzAVng2908KPaFg@mail.gmail.com \
--to=ler762@gmail.com \
--cc=cygwin@cygwin.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).