Re: [boost] [filesystem][v3] Class path codecvt argument now available for appropriate functions

Subject: Re: [boost] [filesystem][v3] Class path codecvt argument now available for appropriate functions
From: Alexander Lamaison (awl03_at_[hidden])
Date: 2010-06-24 19:51:18

On Thu, 24 Jun 2010 16:22:26 -0400, Beman Dawes wrote:

>>> That's great, but where does that leave path::imbue? I think it should
>>> be deprecated. What do others think?
>>
>> I'd be inclined to leave it for those that always want a single codecvt facet, but I have no horse in this race.
> 
> It is still in for the moment. I guess I don't feel strongly about it.

I'd say leave it.  Just because I want to use specific path encodings here
and there doesn't mean I don't want a custom default.  If you remove the
global imbue, my only alternative in that situation would be to imbue every
path individually.

Alex

-- 
Easy SFTP for Windows Explorer (http://www.swish-sftp.org)