lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4835 Move Cal


From: Auto mailings of changes to Lily Issues
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4835 Move Callback_wrapper class to separate file and simplify
Date: Sun, 01 May 2016 08:44:41 +0000

Patch on coutndown for May 4th.


[issues:#4835] Move Callback_wrapper class to separate file and simplify

Status: Started
Created: Thu Apr 28, 2016 06:15 AM UTC by pkx166h
Last Updated: Fri Apr 29, 2016 02:20 PM UTC
Owner: David Kastrup

Move Callback_wrapper class to separate file and simplify

Callback_wrapper::make_smob now is only templated on the address of
the (static) trampoline function. Moving the trampolining to the
actual functions in question makes callbacks quite more versatile and
transparent and obviates the previous need for friend declarations due
to mixing internals of other classes into the Callback_wrapper
definition.

http://codereview.appspot.com/294390043


Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

reply via email to

[Prev in Thread] Current Thread [Next in Thread]