Creation of atomic_futures173 (11/19/2009 9:31:11 PM) 30.6.8/1 ([futures.atomic_future]/1) in N3000 says
The class template atomic_future defines a type for asynchronous return
objects. An atomic_future object can only be created by use of a promise
... Scott
[variadic templates]n-th element of pack expansion syntax proposal076 (11/19/2009 9:58:01 PM) As mentioned in a post of comp.std.c++:
http://preview.tinyurl.com/yzg3dk5
there's a need for some way to get the nth element of a pack
expansion; however, the above post claims:
This is probably th... Larry
The behavior of streambuf::seekoff0110 (11/18/2009 2:31:35 AM) It seems like return type of this function is a tad cloudy in the case
where the last parameter is both std::ios_base::out and
std::ios_base::in . To put it simply, is the returned offset the
calculated offs... sairony(2)
Are call wrappers move-enabled?178 (11/17/2009 6:27:50 PM) [func.require]/4 (20.7.2/4 in N3000) says that call wrappers (such as are
returned from std::bind) must be copy constructible, but it says nothing about
such wrappers being movable. Does this mean that in
... Scott
Smart Pointers organizational logic in draft C++0x2113 (11/17/2009 12:58:15 AM) I see that in the latest draft of C++0x (N3000), unique_ptr (which
syntactically
acts like a pointer, i.e., overloads operator* and operator->) is still not
listed under "Smart Pointers," and weak_ptr (whic... Scott
C++0x, N2960, rvalue reference issues285 (11/12/2009 7:24:40 PM) It seems there are still some places in N2960 where the term "rvalue"
is used without having accounted for rvalue references:
"1.3.4.: The dynamic type [...] [Example: if a pointer p whose static
type is... s.gesemann(661)
Parameter names/types of main function270 (11/13/2009 12:22:36 AM) Is any of the following guaranteed to compile?
int main(int argc, char **argv) { }
int main(int, char **) { }
int main(int argc1, char* argv1[]) { }
int main(int const argc, char* argv[]) { }
int main(in... Johannes
Changes to C++0x made at last standardization meeting389 (11/14/2009 2:38:40 AM) My understanding is that the following changes were agreed upon in the last
standardization meeting:
- std::thread's variadic constructor is to be retained.
- std::async taking variadic arguments is to be ad... Scott
equality and inequality operations need not be defined for output iterators0100 (11/12/2009 7:24:14 PM) The standard says that equality and inequality operations might not be
defined for output iterators. I think the reason for this is that the
standard library algorithms which use output iterators, will only
... subramanian100in