[Lilypond-auto] Issue 4398 in lilypond: Patch: Move the protection of various variables to Protected_scm

[lilypond]

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

New issue 4398 by address@hidden: Patch: Move the protection of various  
variables to Protected_scm
https://code.google.com/p/lilypond/issues/detail?id=4398

Move the protection of various variables to Protected_scm

protect ()/unprotect () are the basic mechanism for starting the
life-time of a Scheme Smob in a non-collectable state until it gets
referenced by some Scheme data structure.  Conflating this temporary
protection with permanent protection makes it harder to gather
meaningful statistics and to do memory allocation debugging.  So this
patch series makes sure that protect/unprotect is really only used
properly paired and for temporary protection.


Consists of commits:

Move the protection of all_fonts_global to Protected_scm

Previously, this abused the protect/unprotect mechanism only intended
for temporary protection.

Also turns All_font_metrics into a Scheme Smob.


Move the protection of global_translator_dict to Protected_scm

Previously, this abused the protect/unprotect mechanism only intended
for temporary protection.


Move the protection of default_global_scale to Protected_scm

Previously, this abused the protect/unprotect mechanism only intended
for temporary protection.

http://codereview.appspot.com/233560043

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