[fpc-pascal] Re: State of fcl-stl generics lib

[Florian Klämpfl]

Am 20.01.2013 14:39, schrieb leledumbo:
>> Indeed, but the additions should follow a common goal and as far as I 
> understood, fcl-stl shall provide opaque containers which is not the 
> case for a tree implementation.
> 
> I thought a better goal would be to have arbitrary data structures that's
> commonly used with generic content, and tree is often a missing pearl from
> other stl-like packages (original C++ STL, 

Where does the C++ STL expose a tree? It might be used internally by a
map or set but I'am not aware of any tree class in the C++ STL.

> Java CF, etc.). File system
> hierarchy, state space searching, ast, etc. all of them uses tree. 

Internally, yes.

> In fact,
> IMHO AVLTree should also be included in fcl-stl, since the current content
> data type is pointer, which is NOT typesafe, and it's better to replace it
> with a generic data type placeholder.
> 
> Furthermore, stl shouldn't be limited to containers. C++ STL has <algorithm>
> doesn't it?

Yes. But since we miss subroutine templates/generics this will be hard
to achieve.