Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c++ Subject: Re: How to get standard paths?!? Date: Sun, 25 Aug 2019 06:38:42 -0700 Organization: A noiseless patient Spider Lines: 18 Message-ID: <864l251i1p.fsf@mailhub.linuxsc.com> References: <_ZR5F.12655$hJ3.11614@fx07.am4> <7cb6F.89442$GfB1.45648@fx36.am4> <868srh1kyz.fsf@mailhub.linuxsc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="39ab2ef3b4360676486225570f5beddf"; logging-data="24572"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX195yndfzfKVeuvirChe/ZDYwGh7Wo/HK/4=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:rfQKuoRCvYC77AK995vxmE3r9jk= sha1:Rx3JvPQqqSgepM8WzUghJ11jWZg= Xref: csiph.com comp.lang.c++:67941 Bonita Montero writes: >> C and C++ implementations must support the locale-specific native >> environment (assuming a hosted implementation in C). They don't >> get to choose what that is; they are required to document it, >> but the standards do not AFAICT give any freedom to choose it. >> If the native environment in MS Windows has more than 65K characters >> then the implementation is non-conforming. > > Quote the part of the C++-standard that says this. In N4659: Section 25.5.1 p1: "The contents and meaning of the header are the same as the C standard library header ." Section 2 (Normative references) p2: "The library described in Clause 7 of ISO/IEC 9899:2011 is hereinafter called the /C standard library/."