From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-04-09 00:51:33
>> I think this solution has a drawback. The approach we were discussing
>> allows the user to obtain wstring from wchar_t command line now, without
>> writing any code at all. What he does with that wstring is up to him but
>> he gets the string.
>> I'm afraid that if user can't get this out-of-box, it's hard to say that
>> 'program_options supports unicode'.
> I didn't think there was an expectation that things would work
> with Unicode, given the various Unicode formats and markers (or
> whatever Miro called them). Perhaps you're saying that a strict
> pass-through, without any conversions to other types, will work.
Yes, that's what I mean.
> I still don't know how you'll parse command lines with Unicode
> unless you know how to find each character.
In UTF-8, I can search for '=', and '-' with a regular string's 'find'
method (except for composing characters problem, but that's minor issue).
That's why it's attractive.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk