This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
__default_allocate_template<>::[de]allocate --- move to supc++?
- From: Ken Yarnall <yarnall at lvc dot edu>
- To: libstdc++ at gcc dot gnu dot org
- Date: Thu, 16 Jan 2003 13:57:54 -0500
- Subject: __default_allocate_template<>::[de]allocate --- move to supc++?
- Organization: Lebanon Valley College
Folks,
Pardon the interruption; hope this is an appropriate place for this.
Short question: libstdc++-v3/src/stl-inst.cc instantiates
__default_alloc_template (or __malloc_... if you go that route), and these
instantiations apparently become a part of libstdc++.
Is it possible for them to shift to libsupc++, or do they in turn depend
on bits of libstdc++? I have a little project that seems to be
independent of libstdc++ except for this instantiation.
I tried an experiment of making my on instantiation of that template in my
source, and linking with libsupc++ only, and things work fine. This
appears to allow me to use map (and perhaps most other containers?)
without linking to libstdc++, at least in some cases.
Cheers,
Ken
--
Ken Yarnall
Dept. of Mathematical Sciences Lebanon Valley College
Assoc. Professor of Math and CS (717)867-6085 yarnall@lvc.edu