Re: [boost] Draft Tutorial / Guidelines for Authors of Boost LibrariesContaining Separate Source

From: Rob Stewart (stewart_at_[hidden])
Date: 2003-11-06 16:59:51

From: "John Maddock" <john_at_[hidden]>
> 
> I've put together a set of draft guidelines come tutorial for libraries that
> have separate source code - this is really just a distillation of my
> experience with the regex library, updated to reflect Rene's forthcoming
> install code.  Most of what follows is unashamedly Windows centric, there
> being much fewer issues effecting Unix shared libraries.  It also doesn't
                          ^^^^^^^^^
affecting

> Fixing the ABI of the Compiled Library
> 
> 
> 
> There are some compilers (mostly Microsoft Windows compilers again!), which
> feature a range of compiler switches that alter the ABI of C++ classes and
> functions.  By way of example, consider Borland's compiler which has the
> following options:
> 
> 
> 
> -b    (on or off - effect emum sizes).
                     ^^^^^^
affects

> -Vx   (on or off - empty members).
> 
> -Ve   (on or off - empty base classes).
> 
> -aX   (alignment - 5 options).
> 
> -pX   (Calling convention - 4 options).
> 
> -VmX  (member pointer size and layout - 5 options).
> 
> -VC   (on or off, changes name mangling).
> 
> -Vl   (on or off, changes struct layout).
> 
> 
> 
> These options are provided in addition to those effecting which runtime
                                                  ^^^^^^^^^
You guessed it: affecting

Those were the things that stood out during my quick read.

It's good to document best practices in this area.  Good work.

-- 
Rob Stewart                           stewart_at_[hidden]
Software Engineer                     http://www.sig.com
Susquehanna International Group, LLP  using std::disclaimer;