mailing list of musl libc
 help / color / mirror / code / Atom feed
From: aep <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: [PATCH] In C++ wchar_t is a keyword, so don't define it
Date: Mon, 10 Oct 2011 16:50:14 +0200	[thread overview]
Message-ID: <e19021bbd45cfde8ede4bce8acc6e598@exys.org> (raw)
In-Reply-To: <5d8e23615cafaa53ffe3825157f7a489@exys.org>


>> imho you meant
>>
>> #ifndef __cplusplus
>> #ifdef __WCHAR_TYPE__
>> TYPEDEF __WCHAR_TYPE__ wchar_t;
>> #else
>> TYPEDEF long wchar_t;
>> #endif
>> #endif



no you are correct. My version only worked by random chance.
Yours is correct.
git send-mail fails me again though, so i can't resubmit right now.


      reply	other threads:[~2011-10-10 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 10:33 Arvid Picciani
2011-10-10 12:23 ` Szabolcs Nagy
2011-10-10 10:33   ` Arvid Ephraim Picciani
2011-10-10 14:03   ` aep
2011-10-10 14:50     ` aep [this message]

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=e19021bbd45cfde8ede4bce8acc6e598@exys.org \
    --to=aep@exys.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).