This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 09 Jul 2015 20:42, Craig Ringer wrote: > On 9 July 2015 at 18:01, Mike Frysinger <vapier@gentoo.org> wrote: > > On 09 Jul 2015 10:15, OndÅej BÃlka wrote: > >> On Wed, Jul 08, 2015 at 02:10:40AM -0400, Mike Frysinger wrote: > > >> > i don't know about a portable answer, but perhaps extending nl_langinfo would > >> > be more on the painless side of things ? adding a GNU-specific keyword that'd > >> > return a hash of the collation data so you could easily check. </naive> > > It'd want to be per-collation, so you don't do unnecessary work if a > locale you aren't using changes. nl_langinfo operates on the current locale, so you'd have to take care of matching the two pieces of data together. > Is there any sane, generic way we might generate a collation > "fingerprint" application-side? Or anything within glibc that could > help? your best bet for something now would be to maintain a structure that fingerprinted collation data in specific glibc versions and then check the current version at runtime. yes, it'd require a good amount of effort and the code would always be behind, but it would work(ish). -mike
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |