This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Fwd: [PATCH] tdestroy() should allow passing 'NULL' for 'freefct' callback
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Ivo Raisr <ivosh at ivosh dot net>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 25 Jun 2013 14:32:31 -0700 (PDT)
- Subject: Re: Fwd: [PATCH] tdestroy() should allow passing 'NULL' for 'freefct' callback
- References: <CANXv6=sw64PRodqTgArqUHQLTcQd8eEE_==6QHVHgLn52jh=1Q at mail dot gmail dot com> <20130611081615 dot GA6224 at domone dot kolej dot mff dot cuni dot cz> <CANXv6=vaJwfOKGgNWU55j-xdB5zqhp5_-3tdjS287+UR1r-nDA at mail dot gmail dot com> <CANXv6=sKC3wsF5ZN9So9Pq=BAfcwvveNZHaSvWEZL5KceH+goQ at mail dot gmail dot com>
This is a user-visible change, so needs a BZ. Probably this should use a
new symbol version. The compat routine need not behave any differently.
But when someone builds a new program that might rely on the new behavior,
they should get a symbol version dependency that ensures that attempting to
run that program against an older library will give a coherent
binary-compatibility error rather than just crashing in tdestroy.