[Lilypond-auto] Issue 4378 in lilypond: Patch: Rewrite Protected_scm for static lifetime requirements

[lilypond]

Status: Started
Owner: address@hidden
Labels: Type-Enhancement Patch-new

New issue 4378 by address@hidden: Patch: Rewrite Protected_scm for static  
lifetime requirements
https://code.google.com/p/lilypond/issues/detail?id=4378

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

http://codereview.appspot.com/238060043

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings