[propertytree] Own storage
Are end users allowed to provide own parsers to populate property tree? For example for the (not yet available) Windows Registry? Or is this discouraged? If not then maybe adding a simple example to the documentation would be a good idea? Adam Badura
Adam Badura wrote:
Are end users allowed to provide own parsers to populate property tree? What do you mean by allowed and provide?
You can of course write whatever parsers you want. You can also share it with other people. The library is open-source, and I have neither the right nor the intention of doing anything to stop you. As for getting other parsers into the library itself, that's a decision I'll have to make on a case by case basis. Every parser I add is, of course, a maintenance burden. But you're free to post the parsers you write and I'll have a look at them. Sebastian
What do you mean by allowed and provide?
You can of course write whatever parsers you want. You can also share it with other people. The library is open-source, and I have neither the right nor the intention of doing anything to stop you.
What I meant is whether the library is fixed in such a way that after writing a working parser I can be sure it will work with next version as well. Adam Badura
Adam Badura wrote:
What do you mean by allowed and provide?
You can of course write whatever parsers you want. You can also share it with other people. The library is open-source, and I have neither the right nor the intention of doing anything to stop you.
What I meant is whether the library is fixed in such a way that after writing a working parser I can be sure it will work with next version as well. Well, the parsers use the same interface as normal clients of the tree, so they have the same interface stability guarantees. (Read: none, but I do my best to avoid breaking the interface.)
Sebastian
participants (2)
-
Adam Badura -
Sebastian Redl