Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c++ > #8311 > unrolled thread

File stream names

Started by"Fraser Ross" <z@z.com>
First post2011-07-29 10:48 +0100
Last post2011-07-30 12:16 -0700
Articles 4 — 4 participants

Back to article view | Back to comp.lang.c++


Contents

  File stream names "Fraser Ross" <z@z.com> - 2011-07-29 10:48 +0100
    Re: File stream names Victor Bazarov <v.bazarov@comcast.invalid> - 2011-07-29 09:17 -0400
    Re: File stream names "Bo Persson" <bop@gmb.dk> - 2011-07-29 16:52 +0200
    Re: File stream names James Kanze <james.kanze@gmail.com> - 2011-07-30 12:16 -0700

#8311 — File stream names

From"Fraser Ross" <z@z.com>
Date2011-07-29 10:48 +0100
SubjectFile stream names
Message-ID<4e3281df$0$2261$c3e8da3$e5d14f71@news.astraweb.com>
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?

Fraser. 

[toc] | [next] | [standalone]


#8319

FromVictor Bazarov <v.bazarov@comcast.invalid>
Date2011-07-29 09:17 -0400
Message-ID<j0ubtg$h8a$1@dont-email.me>
In reply to#8311
On 7/29/2011 5:48 AM, 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?

I believe you meant to ask in 'comp.std.c++' (where the rationales for 
standard features are discussed).

V
-- 
I do not respond to top-posted replies, please don't ask

[toc] | [prev] | [next] | [standalone]


#8321

From"Bo Persson" <bop@gmb.dk>
Date2011-07-29 16:52 +0200
Message-ID<99fvo8FaleU1@mid.individual.net>
In reply to#8311
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

[toc] | [prev] | [next] | [standalone]


#8340

FromJames Kanze <james.kanze@gmail.com>
Date2011-07-30 12:16 -0700
Message-ID<3a3ebc9c-4cac-470c-b22a-65142c1f6518@bl1g2000vbb.googlegroups.com>
In reply to#8311
On Jul 29, 10:48 am, "Fraser Ross" <z...@z.com> 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?

The most obvious is that it isn't supported in most OS's.

--
James Kanze

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.c++


csiph-web