libsigc-list 2016-March Archive by Thread (original) (raw)

• Messages sorted by: [ Thread ] [ Date ] [ Author ]
• Other months

Messages are ordered newest-to-oldest in this index. The newest threads will be at the top of this page, the oldest will be at the bottom.

Within a single thread, the first mail note is the START of the thread; the notes following that are in the chronological order of when they were received. So globally, newest messages are at the top, but within a thread, the oldest (the start of the thread) is at the top.

If you think about it, it is confusing. Just go with the flow and everything will be all right.

• [sigc] ANNOUNCE: libsigc++ 2.9.1,Murray Cumming
• [sigc] ANNOUNCE: libsigc++ 2.99.2,Murray Cumming
• [sigc] std::function<>-style declarations,Murray Cumming
• [sigc] ANNOUNCE: libsigc++ 2.99.1,Murray Cumming
• [sigc] git repo renamed to libsigcplusplus,Murray Cumming
• [sigc] libsigc++-3.0 ?,Murray Cumming
• [sigc] Deprecate retype() and retype_return() ?,Murray Cumming
• Re: [sigc] Deprecate retype() and retype_return() ?,Regis Duchesne
• [sigc] C++11 'auto' with sigc::mem_fun doesn't track object lifetime (potential crash),Andrejs Hanins
• Re: [sigc] C++11 'auto' with sigc::mem_fun doesn't track object lifetime (potential crash),Paul Davis
  • Re: [sigc] C++11 'auto' with sigc::mem_fun doesn't track object lifetime (potential crash),Andrejs Hanins
    * Re: [sigc] C++11 'auto' with sigc::mem_fun doesn't track object lifetime (potential crash),Kjell Ahlstedt
    * Re: [sigc] C++11 'auto' with sigc::mem_fun doesn't track object lifetime (potential crash),Kjell Ahlstedt
    * Re: [sigc] C++11 'auto' with sigc::mem_fun doesn't track object lifetime (potential crash),Andrejs Hanins
• [sigc] ANNOUNCE: libsigc++ 2.7.1,Kjell Ahlstedt

Mail converted by MHonArc