| commit | 75de197e44a87ba221e7da2480429759a2134d9e | |
| author | Gabor Melis <mega@hotpop.com> | |
| Mon, 16 Feb 2009 21:48:20 +0000 (16 21:48 +0000) | ||
| committer | Gabor Melis <mega@hotpop.com> | |
| Mon, 16 Feb 2009 21:48:20 +0000 (16 21:48 +0000) | ||
| tree | c263d6ad5cbeed87fd9aab7fda976d0245ee98fa | treesnapshot (tar.gz zip) |
| parent | 85e1967527101d2d8a4c0f5d37857cf731690733 | commitdiff |
1.0.25.31: axe GC-{ON,OFF}
... because they are broken, nobody uses them (?), and complicated to
fix.
Rationale:
- There is no way to safely allow gc in a WITHOUT-GCING without making
it entirely useless (nothing like the interrupt protocol with
ALLOW-WITH-INTERRUPTS).
- WITHOUT-GCING implies WITHOUT-INTERRUPTS because interrupts running
with gc disabled may lead to deadlocks (see internals manual on lock
ordering and WITHOUT-GCING) or running out of memory. To adhere to
this contract GC-{ON,OFF} would need to enable/disable interrupts by
setting *INTERRUPTS-ENABLED*, comlicated business for little gain.
... because they are broken, nobody uses them (?), and complicated to
fix.
Rationale:
- There is no way to safely allow gc in a WITHOUT-GCING without making
it entirely useless (nothing like the interrupt protocol with
ALLOW-WITH-INTERRUPTS).
- WITHOUT-GCING implies WITHOUT-INTERRUPTS because interrupts running
with gc disabled may lead to deadlocks (see internals manual on lock
ordering and WITHOUT-GCING) or running out of memory. To adhere to
this contract GC-{ON,OFF} would need to enable/disable interrupts by
setting *INTERRUPTS-ENABLED*, comlicated business for little gain.