From 1643108127819448033 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,40bc29384a77c552 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2002-04-16 08:14:00 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!kibo.news.demon.net!news.demon.co.uk!demon!mail2news.demon.co.uk!not-for-mail From: "Edward Diener" Newsgroups: comp.std.c++ Subject: Re: Messages facet and wide character filename Date: Tue, 16 Apr 2002 15:13:54 GMT Organization: EarthLink Inc. -- http://www.EarthLink.net Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: <7lWu8.12107$L1.1021700@newsread2.prod.itd.earthlink.net> References: <3cb19462$0$11204$4c41069e@reader1.ash.ops.us.uu.net> <3CB239B4.E41D0B98@acm.org> <_yts8.1524$CA6.117218@newsread1.prod.itd.earthlink.net> <3CB2EF4B.DA3C3BBA@acm.org> <3CB36E29.8040709@yahoo.com> <5b15f8fd.0204100745.3580bfe0@posting.google.com> <86u1qisapd.fsf@alex.gabi-soft.de> <86wuvdvypv.fsf@alex.gabi-soft.de> <7JJt8.3357$L1.309058@newsread2.prod.itd.earthlink.net> <3CB833CF.8698EC5F@wizard.net> <86it6ugzlc.fsf@alex.gabi-soft.de> X-Trace: mail2news.demon.co.uk 1018970038 mail2news:25565 mail2news mail2news.demon.co.uk X-Complaints-To: abuse@demon.net X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 NNTP-Posting-Date: Tue, 16 Apr 2002 07:14:27 PDT Lines: 30 Xref: archiver1.google.com comp.std.c++:10630 "James Kanze" wrote in message news:86it6ugzlc.fsf@alex.gabi-soft.de... "James Kuyper Jr." writes: >> Well, the existence of an actual implementation would serve to >> resolve the very same uncertainty you mention. There's not much >> point in allowing wide character file names, unless someone actually >> needs them. > In this particular case, I think that there are implementors willing to > implement it, if there were any agreement as to what the semantics > should be. (The issue has been discussed on the committee mailing > lists, and it is apparent that there is no concensus whatever with > regards to the semantics for machines not supporting wide character file > names natively -- which is the usual situation today.) If there were an implementation for an OS not supporting wide character filenames, the do_open implementation of the std::messages facet could fail by returning -1. I would be interested in learning about other issues involved in this case, even though I am not a standard committee member. Is there a way to do that through the Internet ? --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html ]