From owner-cvs-lib Tue Aug 13 04:28:39 1996 Return-Path: owner-cvs-lib Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08740 for cvs-lib-outgoing; Tue, 13 Aug 1996 04:28:39 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA08729; Tue, 13 Aug 1996 04:28:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id VAA10191; Tue, 13 Aug 1996 21:01:20 +1000 Date: Tue, 13 Aug 1996 21:01:20 +1000 From: Bruce Evans Message-Id: <199608131101.VAA10191@godzilla.zeta.org.au> To: CVS-committers@freefall.freebsd.org, ache@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-lib@freefall.freebsd.org Subject: Re: cvs commit: src/lib/libc/locale collcmp.c Sender: owner-cvs-lib@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Modified: lib/libc/locale collcmp.c > Log: > There is so many places where range comparation (using collate) > needed (much more than I think initially), so I forced to add > new user-visible non-standard function to libc. This is probably OK for applications, but please try not to introduce more nonstandard namespace-polluting names that are referenced from separate libraries (collate_range_cmp is referenced from libgnuregex). BTW, can anyone explain why the following program doesn't dump core when it is linked dynamically? --- extern int alarm; main() { alarm = 1; } --- When this is linked statically, `alarm' is resolved to be the alarm() function in the text segment, so the program dumps core as expected. Bruce