Re: On the cost of libraries

[Colm Smyth <Colm Smyth sun com>]

>> It can also be quite handy when trying to resolve
>> nasty problems, for example when trying to combine
>> two libraries that each expect to be able to override
>> the C++ global new() operator, you can specify a different
>> "global" new() symbol binding for each library!
>
>Uh... I think this would backfire sooner or later. How about using -B group
>or -z groupperm instead?

Why do you think it would backfire? You can't get more explicit than
actually stating precisely the library that contains a symbol
definition.

I didn't know about the -B group and -z groupperm options,  looking
at the man-page I can see they would also be useful in a number
of situations.

Colm.