On Sat, 28 Mar 2009, Modestas Vainius wrote:
> Hello,
> 
> when writing a tool which deals with C++ symbols, I found that feature like
> this would be very useful. You will find the full description in the attached
> patch header (also copy&pasted below). Just to give you an idea of the real
> world usage for this:

I'm reluctant to include any code change without seeing the final tool
that requires those changes. I understand the need to mark symbols in
multiple ways so that specific treatment/conversions are made but I'm not
convinced that reusing the comment-based approach used for missing symbols
is the best choice.

And I might be interested in including that tool directly in dpkg too (or
merging the features directly in dpkg-gensymbols if that's possible).

> DEPRECATED - could be used for a few multiarch specific symbols which symbol
> file preprocessor could turn into normal symbols under certain conditions.
> (this is just an example, I know about that #include is different but limited
> way to do it).

Can you be more specific ?

> PRIVATE - C++ template instantiations and other exported private symbols
> (i.e. those which cannot be found in the headers).

Are such symbols really never used by any binary (even in the same source
package) ?


For easier handling of C++/java symbols it might be interesting to follow
the logic of wildcard symbols that would be converted on the fly i.e. the
debian/pkg.symbols could contain:
 c++:"std::basic_string<wchar_t, std::char_traits<wchar_t>, 
std::allocator<wchar_t> >::find_last_of(std::basic_string<wchar_t, 
std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, unsigned int) 
const" 1.3

And when the symbol "_ZNKSbIwSt11char_traitsIwESaIwEE12find_last_ofERKS2_j"
is encountered, c++filt is called and we can make it match with the source
definition above. We could ensure that each unmangled definition gets used
at least once otherwise we make it appear as missing in the output.

We could possibly integrate a generic prefix scheme to be able to deal
with all case that could be of interest:
 - c++: arch-specific symbol mangling
 - java: (arch-specific?) symbol mangling
 - private-ignore: private symbols to ignore
 - private-include: private symbols to include

> Also current master needs the fix below for man/po/de.po to build:

Thanks. 

Cheers,
-- 
Raphaël Hertzog

Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to