Re: expectation vs requirements for locale facets

2007-08-21 Thread Martin Sebor
Travis Vitek wrote: Martin Sebor wrote: Yes. But notice the text doesn't say anything about time_put_byname or time_get_byname ;-) Well, the standard doesn't say much at all about the *_byname facets. All it really says about them is [21.1.1.2 p4] For some standard facets a standard

RE: expectation vs requirements for locale facets

2007-08-21 Thread Travis Vitek
Martin Sebor wrote: The C and C++ standards only specify the requirements on the C locale and leave the localized behavior unspecified. So pretty much anything goes. I don't know how you can say that with a straight face. The C++ standard says that time_put::put() treats the format string

RE: expectation vs requirements for locale facets

2007-08-21 Thread Travis Vitek
Travis Vitek wrote: The strptime() function is clearly skipping leading whitespace with the '%e' flag on those platforms that allow this test to pass. Here is a quick test matrix Doh! I messed up the header row on that table, which might have caused some confusion. Here is the corrected

Re: expectation vs requirements for locale facets

2007-08-21 Thread Martin Sebor
Travis Vitek wrote: Martin Sebor wrote: The C and C++ standards only specify the requirements on the C locale and leave the localized behavior unspecified. So pretty much anything goes. I don't know how you can say that with a straight face. How do you know what face I made when I said

RE: expectation vs requirements for locale facets

2007-08-21 Thread Mark Brown
-Original Message- From: [EMAIL PROTECTED] Sent: Mon, 20 Aug 2007 05:20:32 -0600 To: stdcxx-dev@incubator.apache.org Subject: RE: expectation vs requirements for locale facets Mark Brown wrote: In my experience, the time_get facet isn't always able to reliably parse

RE: expectation vs requirements for locale facets

2007-08-20 Thread Travis Vitek
Martin Sebor wrote: Yes. But notice the text doesn't say anything about time_put_byname or time_get_byname ;-) Well, the standard doesn't say much at all about the *_byname facets. All it really says about them is [21.1.1.2 p4] For some standard facets a standard ..._byname class, derived

RE: expectation vs requirements for locale facets

2007-08-20 Thread Travis Vitek
Mark Brown wrote: In my experience, the time_get facet isn't always able to reliably parse international times and cannot parse every time string produced by the time_put facet. Yes, I see two different problems here. You can generate output with time_put::put for which there is no

RE: expectation vs requirements for locale facets

2007-08-20 Thread Travis Vitek
Test case? Yeah. See attachment. Only tested on Win32/VC8 and Linux/GCC. There is a small bug in the provided testcase. The 'src' struct tm needs to be fully initialized before it can be used for formatting data. This isn't directly related to the problem that I'm running into, but it does

Re: expectation vs requirements for locale facets

2007-08-19 Thread Martin Sebor
Travis Vitek wrote: Travis Vitek wrote: Travis Vitek wrote: The problem is that some locales pad their date/time output with whitespace [like '7. 6. 1988' or ' 7.6.1988'] and I'm unable to use num_get::get_[time,date] to read what is written by num_put::put. It is my understanding that I