Finished transitioning to using gc_refs to track gc objects' states.
This was mostly a matter of adding comments and light code rearrangement. Upon untracking, gc_next is still set to NULL. It's a cheap way to provoke memory faults if calling code is insane. It's also used in some way by the trashcan mechanism.
T
Tim Peters committed
6fc13d9595ef4972551c0dfa7920f8d87935388a
Parent: 8e8dc41