On Wed, Nov 25, 2015 at 2:06 PM, Jacob Champion <champio...@gmail.com> wrote:
> My two cents: I agree that another "name mangled" abbreviation is not > particularly helpful, but I also agree with Jim's concern: "apr_token" made > me immediately wonder what made this exclusive to HTTP tokens. > Unfortunately I don't have much of an alternative suggestion. I have seen > other frameworks refer to an "invariant" or "independent" locale/culture > before; maybe that helps jog someone's creativity? > > Feel free to ignore my rambling. ;) My default naming strategy is to throw > out random ideas. > I was thinking "_lcc_" for locale-C, short and to the point, but meaningful? "_lcposix_" is also descriptive but long, and "_posix_" is much too overloaded with multiple meanings and implications (locales *are* a posix API :)
