Re: dbfunctions - it's over

[Krzysztof Dabrowski]

>I'm a c programmer, but I read this kind of documentation as a designer 
>who has to decide whether the patches are suitable for his needs or not. 
>The c programmer side comes later, when I want to try them.
>I'm going to study/install/patch nothing if I have not clearly understood 
>what the code was designed for.
>And I've not understood (as end user and main designer of my systems) what 
>your patches are going to do.
>
>I think you should add a more wide and clear presentation of your patches 
>and their goals before the c programmer documentation.

there is more info in the readme inside. + the patche's functionality was 
described here more than once.
Everything is just a matter of asking "how this particular thing works" if 
you spot a weak point in the docs.

Kris