0.9.13.47: Thread safety miscellania
authorNikodemus Siivola <nikodemus@random-state.net>
Sun, 18 Jun 2006 23:47:57 +0000 (23:47 +0000)
committerNikodemus Siivola <nikodemus@random-state.net>
Sun, 18 Jun 2006 23:47:57 +0000 (23:47 +0000)
commitebc0f0ebf9efd39519ab86ba28c33abdb25443e0
tree22a6149725caa8752e62d0dc0a4aa250f12ca43d
parentfdf46e7bd7aba9b5c8af629fdb2692d9b33b9207
0.9.13.47: Thread safety miscellania
  * Use localtime_r and gmtime_r instead of thread-unsafe variants
    in time.c.
  * Note gethostby* reentrancy issue in sb-bsd-sockets in BUGS.
  * Trivial PCL cleanups:
    ** *ALL-PV-TABLE-LIST* was unused -- things only got pushed on it,
       but never read. Commented out with a comment, removed code that
       did the pushing.
    ** *INITIAL-PV-TABLE* was unused, deleted.
    ** *EMPTY-PV* was unused, deleted.
    ** *EMPTY-CACHE* was unused, deleted.
    ** *MFP1* & friends implemented a two-element cache outside
       a hash-table. Deleted and replaced with simple hash-table
       access. Boinkmarks will show the truth.
    ** Moved redundant toplevel SETQs to the original DEFPARAMTER
       of various *FOO-COST*s.
    How is this thread-safety related? It happened while flagging
    some PCL globals as safe and others as worthy of attention
    in doc/internals-notes/threading-specials. Also sorted the
    names, so *THE-FOO*s stand out in one place -- seeming to
    me as least-likely causes of trouble.
  * Whitespace.
BUGS
NEWS
doc/internals-notes/threading-specials
src/code/win32.lisp
src/pcl/boot.lisp
src/pcl/cache.lisp
src/pcl/dfun.lisp
src/pcl/vector.lisp
src/runtime/time.c
tools-for-build/grovel-headers.c
version.lisp-expr