Re: [boost] [gsoc] Boost.Process done

Subject: Re: [boost] [gsoc] Boost.Process done
From: Boris Schaeling (boris_at_[hidden])
Date: 2010-08-19 16:43:54

On Thu, 19 Aug 2010 22:13:57 +0200, Ilya Sokolov <ilyasokol_at_[hidden]>  
wrote:

> Boris Schaeling wrote:
>> On Thu, 19 Aug 2010 01:18:56 +0200, Daniel Trebbien  
>> <dtrebbien_at_[hidden]> wrote:
>>
>>> [...]While there is no POSIX equivalent of the wide char functions, I  
>>> was mainly
>>> thinking about using the `TCHAR` macro in cross-platform builds.  
>>> Windows
>>> programmers will probably be programming with TCHAR set to `wchar_t`,  
>>> so if
>>> the process creation library supported templating of the char type,  
>>> then
>>> there wouldn't need to be conversion of wide char strings to narrow  
>>> char
>>> strings. Plus, wouldn't there be a problem trying to execute a module  
>>> on
>>> Windows that has a non-Latin character in it?
>>  Ok, I'll look into it! I don't remember anymore all the details why I  
>> gave up quickly in previous versions. As the implementation has been  
>> simplified maybe it's easier now to support wide chars somehow.
>
> I think we should wait for encoding-aware string class. It will allow to
> solve most of i18n issues in many libraries in a uniform way.
> The libraries I mean are Boost.Asio, Boost.Interprocess, Boost.System,
> Boost.Process and so on.

This would be definitely my preferred solution! Such a library would help  
all others.

Boris