[bind10-dev] STL ABI incompatibility

[Michal 'vorner' Vaner]

Hello

Jinmei pointed out that we might want to hide our vectors from public interface
because of possible incompatibility, because for example debug version of vector
is binary incompatible with non-debug one and therefore it's impossible to plug
these two together.

While this is true, I think we would have a hard time trying to accomplish this,
because we don't have vectors in our data members only, but we pass them in an
out trough methods.

So, I'd like to know, how far are we willing to go to accomplish the binary
compatibility? I know it is a nice goal that the user could just download a new
version and his old plugins would just work. But I believe having to get all stl
out of our headers is quite a lot of work and most users will just use code from
their distro maintainers, who will ensure all parts and external modules
provided by them are binary compatible. The worst that could happen is, I
believe, if someone writes their own module for private use and would have to
recompile it if there's a binary-incompatible change.

How important is the goal to the project? How often do we think it would happen
in practice? Would it be much annoying?

I'd like to decide if we want to accomplish the goal, so we should go and fix
our headers sometime (and not add more problems) or just say we don't want to go
there and easy up the development (and make the code little bit more readable)
by putting some of our data into the headers.

Thanks

-- 
Work with computer has 2 phases. First, computer waits for the user to tell it what 
to do, then the user waits for the computer to do it. Therefore, computer work 
consists mostly of waiting.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20110413/a6d4f783/attachment.bin>