Paul Davis 1e0fd01815 drop boost::signals2 and replace with carl's solution which continues to rely on boost::function and boost::bind but alters two important semantics of signals2: (1) when a Connection object is disconnected, the slot ("functor") associated with the connection is destroyed immediately, unlike signals2 where this is deferred to a subsequent connect/emit call on the signal (2) if one functor called by the signal disconnects another Connection, the functor represented by the Connection will NOT be called during the current signal emission (signals2 copies the slot list at the start of emission and calls everything in the slot list). this change fixes some very nasty crashes apparently caused by boost::signals2 assuming that the memory referenced by a functor remains valid after a disconnect (google will show other developers who had issues with this). ... git-svn-id: svn://localhost/ardour2/branches/3.0@12265 d708f5d6-7413-0410-9779-e7cbd77b26cf		2012-05-14 17:18:48 +00:00
..
boost-debug
macosx
pbd	drop boost::signals2 and replace with carl's solution which continues to rely on boost::function and boost::bind but alters two important semantics of signals2: (1) when a Connection object is disconnected, the slot ("functor") associated with the connection is destroyed immediately, unlike signals2 where this is deferred to a subsequent connect/emit call on the signal (2) if one functor called by the signal disconnects another Connection, the functor represented by the Connection will NOT be called during the current signal emission (signals2 copies the slot list at the start of emission and calls everything in the slot list). this change fixes some very nasty crashes apparently caused by boost::signals2 assuming that the memory referenced by a functor remains valid after a disconnect (google will show other developers who had issues with this).	2012-05-14 17:18:48 +00:00
test	drop boost::signals2 and replace with carl's solution which continues to rely on boost::function and boost::bind but alters two important semantics of signals2: (1) when a Connection object is disconnected, the slot ("functor") associated with the connection is destroyed immediately, unlike signals2 where this is deferred to a subsequent connect/emit call on the signal (2) if one functor called by the signal disconnects another Connection, the functor represented by the Connection will NOT be called during the current signal emission (signals2 copies the slot list at the start of emission and calls everything in the slot list). this change fixes some very nasty crashes apparently caused by boost::signals2 assuming that the memory referenced by a functor remains valid after a disconnect (google will show other developers who had issues with this).	2012-05-14 17:18:48 +00:00
.cvsignore
base_ui.cc	drop boost::signals2 and replace with carl's solution which continues to rely on boost::function and boost::bind but alters two important semantics of signals2: (1) when a Connection object is disconnected, the slot ("functor") associated with the connection is destroyed immediately, unlike signals2 where this is deferred to a subsequent connect/emit call on the signal (2) if one functor called by the signal disconnects another Connection, the functor represented by the Connection will NOT be called during the current signal emission (signals2 copies the slot list at the start of emission and calls everything in the slot list). this change fixes some very nasty crashes apparently caused by boost::signals2 assuming that the memory referenced by a functor remains valid after a disconnect (google will show other developers who had issues with this).	2012-05-14 17:18:48 +00:00
basename.cc
boost_debug.cc	fixes for 98% of all the warnings/errors reported by OS X gcc on tiger	2011-09-30 17:55:14 +00:00
cartesian.cc	switch cartesian/spherical function names and make them use length. still a tweak needed here	2011-02-24 18:55:33 +00:00
ChangeLog
clear_dir.cc
cocoa_open_uri.mm
command.cc
controllable_descriptor.cc
controllable.cc	Slightly unpleasant fix for creation of tracks from	2011-11-16 23:03:59 +00:00
convert.cc	more fixes/tweaks from the land of the lion	2012-05-02 20:45:17 +00:00
COPYING
cpus.cc
crossthread.cc	another quick OS X Lion gcc suggestion	2012-05-02 20:33:39 +00:00
debug_rt_alloc.c	Missing files.	2011-01-19 21:49:14 +00:00
debug.cc	eventloop and abstractui debugging, lots more commenting on abstractui/eventloop implementation; minor tweaks elsewhere	2012-04-24 16:45:38 +00:00
dmalloc.cc
enums.cc	Remove unused bits.	2011-03-04 00:35:01 +00:00
enumwriter.cc	Add basic test of playlist layering.	2011-12-15 14:33:20 +00:00
epa.cc
error.cc
event_loop.cc	eventloop and abstractui debugging, lots more commenting on abstractui/eventloop implementation; minor tweaks elsewhere	2012-04-24 16:45:38 +00:00
file_manager.cc	Fix build.	2011-05-23 22:18:57 +00:00
file_utils.cc
filesystem_paths.cc
filesystem.cc	Save templates as directories with plugin state, if	2011-12-11 20:38:42 +00:00
fpu.cc	explain MXCSR shenanigans in libs/pbd/fpu.cc	2011-12-26 22:32:21 +00:00
gettext.h
i18n.h
id.cc	make Stateful::_id private and provide appropriate methods to set it, and use them throughout ardour	2011-10-18 13:18:47 +00:00
libpbd.pc.in
libpbd.spec.in
locale_guard.cc
malign.cc
mountpoint.cc	complete the do-not-free-data-from-getmntinfo() fix	2012-01-11 18:14:18 +00:00
openuri.cc
pathscanner.cc	remove hard-coded use of '/' in pathscanner code as dir separator (use glib instead)	2011-02-28 16:35:43 +00:00
pool.cc	Fix some set-but-not-used variable warnings from gcc 4.6	2011-07-02 17:16:46 +00:00
property_list.cc
pthread_utils.cc
receiver.cc
run-tests.sh	Fix libpbd tests and add test for url_decode().	2012-04-01 14:29:26 +00:00
search_path.cc
semutils.cc
shortpath.cc
signals.cc	drop boost::signals2 and replace with carl's solution which continues to rely on boost::function and boost::bind but alters two important semantics of signals2: (1) when a Connection object is disconnected, the slot ("functor") associated with the connection is destroyed immediately, unlike signals2 where this is deferred to a subsequent connect/emit call on the signal (2) if one functor called by the signal disconnects another Connection, the functor represented by the Connection will NOT be called during the current signal emission (signals2 copies the slot list at the start of emission and calls everything in the slot list). this change fixes some very nasty crashes apparently caused by boost::signals2 assuming that the memory referenced by a functor remains valid after a disconnect (google will show other developers who had issues with this).	2012-05-14 17:18:48 +00:00
sndfile_manager.cc	Assorted doxygen fixes; no functional changes.	2011-05-23 22:12:45 +00:00
stacktrace.cc
stateful_diff_command.cc
stateful.cc	Clear up confusion with overloads of _frozen and frozen()	2011-12-17 16:37:18 +00:00
strreplace.cc
strsplit.cc
textreceiver.cc
transmitter.cc
undo.cc	actually delete the contents of the history list, rather than just empty the list. could break things at session closing.	2011-02-12 20:57:44 +00:00
uuid_boost.cc	revert earlier changes to uuid class, but keep boost version in svn for the future	2011-02-08 02:21:15 +00:00
uuid.cc	revert earlier changes to uuid class, but keep boost version in svn for the future	2011-02-08 02:21:15 +00:00
whitespace.cc
wscript	remove virtual inheritance of sigc::trackable by Receiver and AbstractUI<T>, done by changing Gtkmm2ext::UI to use composition (HAS-A) rather than inheritance (IS-A) for Receiver; use correct synchronization when starting up a BseUI event loop thread so that tests that start/stop quickly do not encounter a race condition	2012-05-14 17:07:53 +00:00
xml++.cc	some deep changes to xml++ in which we retain a C-level xmlDocPtr as a member of an XMLTree objects. this allows us to do repeated XPATH searches (as in the midnam parser of libmidi++) without constantly rewriting an entire tree into memory to recreate a new xmlDocPtr with which we can search. Since XMLTree objects don't typically stay around for very long, just when serializing to/from disk, this is not anticipated to have much (if any) impact on memory consumption	2012-03-20 18:01:07 +00:00