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

[lilypond]

Updates:
        Status: Fixed
        Labels: -Patch-push Fixed_2_19_21

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

Pushed to staging as
commit addcfaa3225a64aa23d29d9171b721c8a4895ef9
Author: David Kastrup <address@hidden>
Date:   Fri May 8 11:04:01 2015 +0200

    Issue 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.

commit 37d6daa25b4bab4a0971ef84d965d5b6c8e581f0
Author: David Kastrup <address@hidden>
Date:   Fri May 8 11:34:32 2015 +0200

    Avoid gratuitous use of Protected_scm copy constructor


--
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