|
From: | lilypond |
Subject: | Re: [Lilypond-auto] Issue 3907 in lilypond: Patch: Moves the Box class to flower/ in a new class called FlowerBox. Wraps FlowerBox as Box smob in lily/ |
Date: | Mon, 28 Apr 2014 07:43:35 +0000 |
Comment #2 on issue 3907 by address@hidden: Patch: Moves the Box class to flower/ in a new class called FlowerBox. Wraps FlowerBox as Box smob in lily/
http://code.google.com/p/lilypond/issues/detail?id=3907I think that is a bad idea. The reason it is a bad idea is that LilyPond's memory management basically revolves around Scheme objects, and moving complex structures away from Scheme objects means lots of unnecessary copying and/or reference counting.
Moving complex objects like Skyline/Skyline_pair would mean that all of its internal data has to be organized and structured outside of the Scheme data model, and that means that accessing and processing that data from Scheme, if possible at all, will necessitate bulk conversions into Scheme that are inefficient.
The whole enterprise is also fabulously pointless since there already is a much more encompassing, efficient and actively maintained library for that in the form of CGAL <URL:http://www.cgal.org/>, so we are not actually creating tangible benefits for people outside of LilyPond. They are much better off using CGAL (or actually a sizable number of other readily available computational geometry libraries).
--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
[Prev in Thread] | Current Thread | [Next in Thread] |