Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Bo Persson" Newsgroups: comp.lang.c++ Subject: Re: File stream names Date: Fri, 29 Jul 2011 16:52:03 +0200 Lines: 16 Message-ID: <99fvo8FaleU1@mid.individual.net> References: <4e3281df$0$2261$c3e8da3$e5d14f71@news.astraweb.com> X-Trace: individual.net +GzOwmIv231U3EKfA1DOTAD+tsxq88gHQqkfz9BPbAgOW3dlTU Cancel-Lock: sha1:v0Q0IExeT/OUuUzliiwcW0k51Sk= X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-RFC2646: Format=Flowed; Response X-Antivirus: avast! (VPS 110729-0, 2011-07-29), Outbound message X-Antivirus-Status: Clean Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:8321 Fraser Ross wrote: > The standard library allows file name types of char const * and > std::string for opening file based streams. Is there a reason for > omitting the wide character types? > One reason is that nobody has come up with a set of semantics that everybody else can agree on. Things like, what does a wide string mean on a filesystem with narrow char file names? Bo Persson