template containers again
Vaclav Slavik
vslavik at fastmail.fm
Mon Jul 2 04:23:12 PDT 2007
Robert Roebling wrote:
> At first I thought that we should do that, but there is actually
> little sense in doing so.
* It provides better compatibility with STL (in addition to using the
container with STL algorithms, which wxVector would presumably be
complete enough to allow, it lets you pass e.g. wxVector<int> to a
function taking std::vector<int>).
* VS2005 debugger understands (and displays in a usable way) STL
containers out of the box.
* SWIG understands std::vector<> out of the box -- in theory, this
should make it easier to generate wrappings (if they used wxUSE_STL
for the SWIG run).
* If you used std::vector in your code, std::vector<T> and wxVector<T>
would share the (non-inlined) code in compiled binary instead having
two versions of it for every T used.
Regards,
Vaclav
--
PGP key: 0x465264C9, available from http://pgp.mit.edu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wxwidgets.org/pipermail/wx-dev/attachments/20070702/4f88dd55/attachment.pgp
More information about the wx-dev
mailing list