Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion book/the-lox-language.md
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ retain calls if you squint.

For lots more on this, see "[A Unified Theory of Garbage Collection][gc]" (PDF).

[gc]: https://researcher.watson.ibm.com/researcher/files/us-bacon/Bacon04Unified.pdf
[gc]: https://web.eecs.umich.edu/~weimerw/2008-415/reading/bacon-garbage.pdf

</aside>

Expand Down
2 changes: 1 addition & 1 deletion site/the-lox-language.html
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,7 @@ <h3><a href="#automatic-memory-management" id="automatic-memory-management"><sma
opposing sides. Most ref counting systems end up doing some tracing to handle
cycles, and the write barriers of a generational collector look a bit like
retain calls if you squint.</p>
<p>For lots more on this, see &ldquo;<a href="https://researcher.watson.ibm.com/researcher/files/us-bacon/Bacon04Unified.pdf">A Unified Theory of Garbage Collection</a>&rdquo; (PDF).</p>
<p>For lots more on this, see &ldquo;<a href="https://web.eecs.umich.edu/~weimerw/2008-415/reading/bacon-garbage.pdf">A Unified Theory of Garbage Collection</a>&rdquo; (PDF).</p>
</aside>
<p>Tracing garbage collection has a fearsome reputation. It <em>is</em> a little harrowing
working at the level of raw memory. Debugging a GC can sometimes leave you
Expand Down