Locale class>>#englishUS request

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Locale class>>#englishUS request

Esteban A. Maringolo
Hi,

I'm doing some things which requires the printing of dates in RFC1123
string format, among other stuff.

I'm using (Locale lcid: 1033) to obtain the "English (United States)"
locale, I don't know if it get cached between calls, but seeing it
instantiates each time I call it, I think it's not savvy to use it this
way.

Given that this locale is one of the most common for protocol based
operations and other standards, it would be convenient to have it in the
same way as UserDefault and SystemDefault.

Please treat this as a enhancement request.

Thanks in advance.

Regards,

--
Esteban.


Reply | Threaded
Open this post in threaded view
|

Re: Locale class>>#englishUS request

Chris Uppal-3
Esteban A. Maringolo wrote:

> Please treat this as a enhancement request.

While we're on the subject of enhancement requests for Locales -- it would help
if the Locale could cache more data than the currently (rather ugly) hardwired
list of 8 "features":

    dateSeparator
    decimalSeparator
    listSeparator
    timeSeparator
    currencySymbol
    amDesignator
    pmDesignator
    dayNames
    monthNames

I suggest adding a small hash table to each Locale (and maybe downgrade the
less frequently used instvars to be entries in that table).

My localised number printing/parsing stuff would would use that if it were
available -- there are at least 8 additional candidate fields.

    -- chris