stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Vitek" <Travis.Vi...@roguewave.com>
Subject RE: [Stdcxx Wiki] Update of "LocaleLookup" by TravisVitek
Date Thu, 27 Mar 2008 22:52:31 GMT
 

Travis Vitek wrote:
>
>Martin Sebor wrote:
>
>>Travis Vitek wrote:
>>
>>> + || 22.LOCALE.CONS.MT.CPP || *1,+ ||
>>> + || 22.LOCALE.CTYPE.CPP || *2 ||
>>> + || 22.LOCALE.CTYPE.IS.CPP || *2 ||
>>> + || 22.LOCALE.CTYPE.MT.CPP || *1,+ ||
>>> + || 22.LOCALE.CTYPE.NARROW.CPP || *2 ||
>>> + || 22.LOCALE.CTYPE.SCAN.CPP || *2 ||
>>> + || 22.LOCALE.CTYPE.TOLOWER.CPP || *2 ||
>>> + || 22.LOCALE.CTYPE.TOUPPER.CPP || *2 ||
>>
>>I thought the ctype tests were being run in all installed locales,
>>just like the numpunct one? Which is what we want to move away from.
>>IMO, exercising a small set (less than a dozen) of known locales and
>>encodings should be plenty.
>>
>
>Yes, the non-mt ctype tests iterate over each locale for which 
>the function call `setlocale (LC_CTYPE, name)' succeeds. The mt
>ctype tests all limit the number of tested locales to 32.
>

Any suggestions on which languages/countries/codesets that we should
be testing against for the ctype tests?

Reducing the number of selected locales to 32 is pretty easy. Selecting
which locales is a little more difficult. Another issue is that the
mechanism I have defined doesn't support selecting only one locale for
each match.

Travis

Mime
View raw message