This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Nonstandard allocator::pointer in containers


Paolo Carlini wrote:
First blush, I don't see any problem with this change. Actually,
considering for instance std::vector, the search-and-replace amounts to
5 occurrences all inside struct _Vector_base. I'm wondering whether you
can maybe try it yourself and report how it goes.

Thanks Paolo and Chris for your quick and helpful replies.


I may have a look at trying this, but I have a practical question first. I'd like to use this in the next version of anyterm, which will ship well before the next version of libstdc++ (like next week). So I'll need to be able to ship the modified container code with the Anyterm source. So, if I change the small number of headers and put then in a subdirectory and pass a suitable -I flag, will it "just work"? (Am I right in thinking that all of the code is in the headers, or is there stuff in the compiled library as well?) I'm mostly interested in <map>; <string> would be nice but vector<char> would be good enough.

--Phil.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]