Re: CVS commit: src/sys/lib/libunwind

[Martin Husemann <martin%duskware.de@localhost>]

On Wed, Oct 16, 2013 at 05:09:25PM +0200, Joerg Sonnenberger wrote:
> The need was mentioned a number of times in various threads about libc++
> and clang.

But for the kernel? And the details?
Like where to place it and what to use it for?

> >  - why is it placed in src/sys/lib instead of src/sys/external/...?
> 
> Because it is not handled as 3rd party source.

Why not? And what does "heavily modified" (from the import log) mean?

> >  - there is no user in tree yet, why the import upfront?
> 
> This is not true.

Give me hint, please.

> >  - what are the alternatives to this very ugly, undocumented, templated C++
> >    code?
> 
> I won't ever both with this such an opinionated question...

Very true - but the point is, that it would be realy helpfull if you could
not drop such "easter eggs" somewhere hidden in the tree, but explain
reasoning and plans upfront.

I am not a C++ hater, as you probably know, but C++, with templates, and not
even a C API, apparently prepared to be used in the kernel -- IMHO deserves
an introductionary mail, at the very least.

Martin