containers

What's the return of the algorithm std:set_union when one or both input containers are multisets with duplicated objects? Do dups get lost? Let's suppose for example: multiset<int> ms1; ms1.insert(1); ms1.insert(1); ms1.insert(1); ms1.insert(2); ms1.insert(3); multiset<int> ms2; ms2.insert(1); ms2.insert(1); ms2.insert(2); ms2.insert(2); ms2.insert(4); vector<int> v(10); set_union( ms1.begin(), ms1.end(), ms2.begin(), ms2.end(), v.begin() ); What would the output be? From the standard, 25.3.5: The semantics of the set operations are generalised to multisets in a standard way by defining union(

I couldn't find an exact answer to this question and hence posting here. When I think of vector, it needs to build objects in a contiguous memory location. This means that vector keeps memory allocated and have to do an in-place construction (=placement new) of objects being pushed into it. Is this a valid assumption? Also, does this mean the container is manually invoking the destructor rather than calling delete? Are there any other assumptions that I am missing here? Does this mean I can assume that even a custom written new for the object may not be invoked if I chose to write? Also it

I'm trying to make a type-safe generic linked list in C using macros. It should work similarly to how templates work in C++. For example, LIST(int) *list = LIST_CREATE(int); My first attempt was for #define LIST(TYPE) (the macro I used above) to define a struct _List_##TYPE {...} . That, however, did not work because the struct would be redefined every time I declared a new list. I remedied the problem by doing this: /* You would first have to use this macro, which will define the `struct _List_##TYPE`... */ DEFINE_LIST(int); int main(void) { /* ... And this macro would just be an alias for

I am aware of creating web application but there is one basic doubt I have. I am sorry for asking very silly question but want to clear my doubt. How Tomcat Container handle request, I mean to say when I send a request for home.jsp page then I get the response as home.jsp page only and not a register.jsp page which at the same time might be the request given by other person requested from other corner of the world. Eg: Client A --------request(a.jsp)----------> Tomcat (check request received for a.jsp and give proper a.jsp response to client A) Client B --------request(b.jsp)----------> Tomcat

I have read from a book The difference between containers and collections lies in the fact that containers are always open (i.e., new members may be added through additional RDF statements) and collections may be closed. I don't understand this difference clearly. It says that no new members can be added to a collection. What if I change the value of the last rdf:rest property from rdf:nil to _:xyz and add _:xyz rdf:first <ex:aaa> . _:xyz rdf:rest rdf:nil . I am thus able to add a new member _:xyz . Why does it then say that collections are closed? The key difference is that in a Container,