Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(998)

Issue 238060043: Rewrite Protected_scm for static lifetime requirements (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
9 years ago by dak
Modified:
8 years, 11 months ago
Reviewers:
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Rewrite Protected_scm for static lifetime requirements The use of Protected_scm is required where the per-instance object marking mechanisms don't work. This patch changes its semantics to cater exclusively for the use case of permanent variable life time (as opposed to permanent value life time). It no longer employs the reversible scm_gc_protect_object but rather uses scm_permanent_object for protecting one cons cell as its principal storage mechanism. It is also ensured that construction/destruction (which happen at very early/late phases of program execution) do not require a working memory subsystem. Also contains commit: Avoid gratuitous use of Protected_scm copy constructor

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+39 lines, -28 lines) Patch
M lily/grob-property.cc View 2 chunks +3 lines, -3 lines 0 comments Download
M lily/include/protected-scm.hh View 1 chunk +16 lines, -2 lines 0 comments Download
M lily/protected-scm.cc View 1 chunk +20 lines, -23 lines 0 comments Download

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b