list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
/libsigc-list
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http
On Tue, 2005-07-12 at 22:37 +0200, Antonio Coralles wrote:
On http://libsigc.sourceforge.net/libsigc2/docs/manual/html/ch01.html
one can read
'To make it easier to construct these, libsigc++ provides 2 the
sigc::ptr_fun() and sigc::mem_fun() functions ...'
Antonio
Fixed. Thanks.
--
Murray
false.
Is there a way to customize this
behavour ?
[I know that this problem can be easily be circumvented using empty() ... ]
Antonio
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc
On Fri, 2005-01-07 at 12:12 +0100, Murray Cumming wrote:
On Mon, 2004-11-22 at 01:00 -0500, Carl Nygard wrote:
http://www.3sinc.com/opensource/boost.bind-vs-sigc2.html
[snip]
Docs updated.
[snip]
I thought I'd review this again, because I lost track of what changes
were made.
1
to on this is the FSFs
because they have lawyers.
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
++ 2.0 and won't need to
be. If there are enough useful API additions, then we might even release
a tarball of this.
The libsigc-2.0 branch will be for continued maintenance of libsigc++
2.0 releases.
Any objections?
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
On Mon, 2006-06-19 at 22:23 +0200, Murray Cumming wrote:
On Tue, 2006-06-06 at 22:08 +0200, Murray Cumming wrote:
On Tue, 2006-06-06 at 10:17 -0700, Régis Duchesne wrote:
Folks,
I sent this patch (which allows to compile the libsigc++ headers with an
Objective-C++ compiler
On Thu, 2006-07-06 at 18:20 +0200, Aristid Breitkreuz wrote:
Am Donnerstag, den 06.07.2006, 07:58 +0200 schrieb Murray Cumming:
Am Mittwoch, den 05.07.2006, 18:49 +0200 schrieb Ulrich Eckhardt:
That's true. LGPL requires that people are able to relink your
executable with
a modified
to simplify it (writing less code) and make less error-
prone (all is done only once and in one place.) This is at a small
cost to efficiency, which is not important in GUI.
Paul
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
be specialized for what they control.
I suggest that you try to distribute this in a separate library for now.
I'm not sure that people will consider it worthwhile to introduce the
extra concept into their code, but let's see if they like it.
Maybe someone can even make it more generic.
--
Murray
On Sat, 2006-07-08 at 19:54 +0300, Paul Pogonyshev wrote:
Murray Cumming wrote:
I suggest that you try to distribute this in a separate library for now.
I'm not sure that people will consider it worthwhile to introduce the
extra concept into their code, but let's see if they like
.
-Michael
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list
.
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
On Friday 28 July 2006 12:48, Murray Cumming wrote:
Yes, I've had this problem too. You might be able to #undef it.
Any tips for combining sigc++ and Qt would be appreciated.
If it's undefined, Qt won't work properly, as it relies on that word :(.
Well, you'd have to be clever about where
that you'd like to give your improvements back,
I personally prefer to use a licence that forces you to.
For other readers, Yes, I know I need to deal with the LGPL templates
exception thing. I'll get around to it. I notice that nobody has objected
to the draft that was posted.
Murray Cumming
this message.
Qt's emit macro is a well known problem, but I didn't know about
QT_NO_KEYWORDS
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo
prefer the explicit sig.emit() syntax to sig(), but
I can live with it.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
On Wed, 2006-10-11 at 09:45 -0700, Régis Duchesne wrote:
Murray,
Looks good to me. I prefer the explicit sig.emit() syntax to sig(), but
I can live with it.
IIRC, libsigc++ supports both.
Yes. But it looks like TR2 supports just sig().
--
Murray Cumming
[EMAIL PROTECTED
On Wed, 2006-10-25 at 10:59 -0500, Mark Tilford wrote:
SigC is sigc++ v1
sigc is sigc++ v2
Any idea why fink would be pulling the old version?
Both versions should (and might) be available. They install in parallel.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
inheritance is a very odd thing and doesn't act
exactly as you might expect.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
, and you might have your virtual inheritance in the
wrong place. It's worth investigating what gtkmm does.
Bakery also does some complex virtual inheritance.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing
destructors. Performance is one possible reason.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
than signal connection, understandably), and
runtime memory use. If you can improve it, for some future
parallel-installable version of libsigc++, and prove that it's an
improvement, you might try to provide a patch.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
to fix this properly.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
.
It's a dependency of gtkmm, and part of the GNOME Platform Bindings
release sets. It's not going to stop working, and if it did, there's
lots of people who would need to fix it.
Can you enlighten me on the status of the library/project ?
Thanks in advance,
Jesper Juhl
--
Murray Cumming
[EMAIL
On Tue, 2007-05-15 at 00:10 +0200, Jesper Juhl wrote:
On 14/05/07, Murray Cumming [EMAIL PROTECTED] wrote:
On Mon, 2007-05-14 at 22:48 +0200, Jesper Juhl wrote:
Hi,
While looking for a C++ signalt and slots library to use together with
SDL and a few other bits, I stumbled across
to update the docs, apart from that
libsigc++ seems to be quite neat (and the tutorial-style-docs are very
helpful nevertheless!). Now I hope the runtime (per-call) performance is
not too far behind my old, ugly, virtual-method-hook-class-in-std::vector
solution...
--
Murray Cumming
[EMAIL
, but you might have
no choice.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
On Fri, 2006-07-07 at 00:20 +0100, Chris Vine wrote:
On Thursday 06 July 2006 06:58, Murray Cumming wrote:
As stated in that previous email, at some point we should explicit state
this in an exception in the headers, but I haven't got around to it, and
nobody has cared enough to write
this as another of these non-authoritative contributions
to
a license discussion thread.. ;-/ (FWIW, I repeatedly read the above on the
kde-core-devel list.)
Which doesn't make it correct.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
++ needs to get a workaround for this compiler bug.
Maybe. Patches are welcome.
In general, I believe that the non-static Visual Studio build works fine
for gtkmm.
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list
++/object_slot.h
using namespace SigC;
[snip]
libsigc++ 2.0 uses the sigc namespace. You have maybe found an old
example. The libsigc++ tarball contains working examples for its
version.
Do you have some working example with compilation instructions?
In advance, thank you very much.
Murray
On Fri, 2007-11-09 at 19:01 -0500, Buğra Gedik wrote:
If I have a signal connected to a slot and once the connection is
established, can I run multiple threads that call emit() on the same
signal. In other words, is the emit() function thread-safe? From my
examples, it seems it is not.
No,
On Mon, 2007-07-09 at 21:02 +0200, Murray Cumming wrote:
On Sun, 2007-06-17 at 08:19 -0700, Daniel Burrows wrote:
Hi all,
I've been doing some test builds with g++-4.3 (on Debian, naturally),
to see what sort of preparation will be needed before it's released as
stable. One
On Sat, 2007-12-08 at 09:38 -0800, Daniel Burrows wrote:
On Sat, Dec 08, 2007 at 02:54:16PM +0100, Murray Cumming [EMAIL PROTECTED]
was heard to say:
On Mon, 2007-07-09 at 21:02 +0200, Murray Cumming wrote:
On Sun, 2007-06-17 at 08:19 -0700, Daniel Burrows wrote:
The typedef
On Thu, 2008-05-01 at 21:18 +0200, Milosz Derezynski wrote:
Hello,
I've built a Debian Package for Hardy Heron of sigx, it's available
here: http://futurepast.free.fr/debian/
Thanks.
Please do open an Ubuntu bug about it, so it can go into the official
repository.
--
[EMAIL PROTECTED]
On Tue, 2008-06-10 at 18:16 +0530, Jinesh K J wrote:
hi,
I have a small doubt,
i have a code which written using the headers and related files for
libsigc++20-2.0.17-2. I now use a fedora 9 machine. It is having
libsigc++20-2.2.2-1. As there is only a minor version difference i
thought
On Tue, 2008-06-10 at 18:58 +0530, Jinesh K J wrote:
hi,
I have to check it myself and i found a little solutions. i am using
only SigC::slot is sigc::slot the same?
Yes.
--
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list
.
- Paul Goins
___
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
--
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
libsigc-list
doesn't work with classes that have an overloaded operator(), but you
can always use a lambda for those cases.
Is this something that we should add to libsigc++? If so, it would be
great to have a patch, with a test case too.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
www.openismus.com
On Fri, 2012-01-06 at 19:15 +0800, Chow Loong Jin wrote:
On 06/01/2012 03:16, Rui Maciel wrote:
On 01/05/2012 04:05 PM, Chow Loong Jin wrote:
The only macro I can find to do with detecting C++0x is
__GXX_EXPERIMENTAL_CXX0X__ which is probably not portable. __cplusplus is
supposed to be
On Sat, 2012-01-07 at 22:15 +0800, Chow Loong Jin wrote:
On 06/01/2012 21:21, Murray Cumming wrote:
Instead of checking for particular compiler versions, we would generally
add a test that is run during configure time. That would test for the
compiler capability. There are already several
On Tue, 2012-07-31 at 08:55 -0400, Paul Davis wrote:
using sigc++ and Qt could be problematic.
Not particularly. You have to be careful about the Qt headers defining
things like slot, but you can disable them by defining QT_NO_KEYWORDS.
Google found this example of someone doing this:
= on_print;
signal_print.connect(slot);
signal_print.emit(hello world\n);
return 0;
}
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman
-list
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
www.openismus.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
the new syntax compared to sigc::mem_fun(), but
we should expect people to want to use sigc::function now that it is
officially part of C++. And we could always leave sigc::mem_fun() as a
convenient way to create a std::function.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list
/libsigc++/unstable/
*** Changes
2.9.1 (unstable):
* slot: Allow sigc::slot<R(Args...)> syntax, like std::function,
deprecating the sigc::slot<R, Args...> syntax.
(Murray Cumming, Kjell Ahlstedt) Bug #763393
* signal: Allow sigc::signal<R(Args...)> syntax, like std::funct
installs in
parallel with libsigc++-2.0. The API is not significantly different,
but the implementation is far simpler, using variadic templates instead
of generating C++ code from .m4 files.
libsigc++-3.0 requires a compiler with C++14 support.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
, in a future gtkmm-4.0.
That's because, even though libsigc++ is mostly template code in header
files, its symbols appear in glibmm and gtkmm symbols names, for
instance for method parameters.
Objections? Thoughts?
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
. Also,
the ++ seems to have broken mirroring on github. That should work again
soon, and maybe we could even accept pull requests that way too.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
On So, 2016-04-24 at 16:03 +0200, Kjell Ahlstedt wrote:
> Den 2016-04-24 kl. 15:20, skrev Murray Cumming:
> > On So, 2016-04-24 at 13:21 +0200, Kjell Ahlstedt wrote:
> > >
> > > There are signal_base::block()/unblock() methods, but they don't
> > > do
&
On Sa, 2016-04-23 at 20:17 +, James Lin wrote:
> Murray Cumming wrote:
> >
> >
> > Does anyone actually use sigc::signal<>::slots() to iterate over
> > connected slots or to remove or add connected slots?
> Is there an alternate mechanism to iterate ov
ase already provided
> block/unblock methods. (Looks like it was introduced in 2.3.x.)
> That's unfortunate since it means that I'm now asking to change
> existing behavior. Drat.
It feels more like a fix than a major change of behaviour. Maybe we can
fix that at least for now, so we feel better
functor_base base class, and functors no longer need to have
a result_type typedef or alias.
(Murray Cumming)
* emitters and accumulators no longer need to have a result_type
typedef or alias.
(Murray Cumming)
* Remove now-unnecessary adaptor_type type aliases.
(Murray Cumming)
* Remove some
t from libsigc++-3.0. It
would reduce some need to keep track of object lifetimes.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
bug with a full (but small
as possible) test case. Thanks.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
rrored and some not.
Actually, most GNOME developers seem to wish that the mirror didn't
exist, particularly as we cannot tell people not to create pull
requests there until they've already done so.
And GNOME isn't unlikely to really start using github now that they
have their own gi
On Wed, 2018-02-21 at 21:11 +0100, Murray Cumming wrote:
> Projects are now gradually moving from git.gnome.org to
> gitlab.gnome.org, which certainly looks like an improvement. However,
> rather than use GNOME's git, maybe we should just move libsigc++ to
> github. GNOME has been a r
old git.gnome.org git repo as unused,
and gradually even move the bugzilla issues to github.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
not a particularly GNOME
project.
Any major objections?
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
here to store libsigc++
> in the future.
Thanks. I'm not greatly troubled that that, though it is a bit odd.
Either continuing to release tarballs on gnome servers, or just using a
tarball in jhbuild, are not great disadvantage.
--
Murray Cumming
murr...@mur
On Sat, 2018-02-24 at 17:56 +0100, Murray Cumming wrote:
> Actually, creating a github organisation is easier than I thought.
>
> How about this?
> https://github.com/libsigcplusplus/libsigcplusplus
>
> If nobody objects, I'll mark the old git.gnome.org git repo as
> unused,
itHub issues.
Yes. There's no rush.
> The forth open bug, https://bugzilla.gnome.org/show_bug.cgi?id=306705
> , was filed 13 years ago. I suggest that we don't copy it to GitHub.
> Perhaps close it as WONTFIX?
I guess so, yes.
Thanks.
--
Murray Cumming
murr...@
compile times (maybe not significant in this case).
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
___
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
here's a real possibility that we'll only learn about the
need for some API-breaking change once we've had the attention that a
.0 release brings. But until gtkmm 4.0.0 happens, we'd still have a
chance to do a libsigc++ 4.0 if necessary.
Kjell, would you like to take care of doing a 3.0.
.)
Maybe someone would like to create a PR to build with MSVC on Windows
too? See, for instance:
https://help.github.com/en/articles/virtual-environments-for-github-actions#supported-virtual-environments-and-hardware-resources
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
On Sat, 2019-09-28 at 14:19 +0200, Murray Cumming wrote:
[snip]
> Maybe someone would like to create a PR to build with MSVC on Windows
> too? See, for instance:
> https://help.github.com/en/articles/virtual-environments-for-github-actions#supported-virtual-environments-and-hardware-reso
he changes a bit messy:
https://github.com/libsigcplusplus/libsigcplusplus/pull/31
Option 1 (changing the PATH) seems to be the simplest and most correct
way to do it, but I haven't found quite the correct CMake incantation:
https://github.com/libsigcplusplus/libsigcplusplus/pull/32
If you have a
turn on warnings-as-errors in the
CMake/MSVC build, and maybe how to turn on some more warnings, we might
get something useful from MSVC. Please do create a Pull Request if you
figure that out. Thanks.
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
73 matches
Mail list logo
