On Wed, Feb 8, 2012 at 7:49 PM, Hugo Parente Lima <hugo.l...@openbossa.org>wrote:
> Cons: > > - We will somehow loose a never used flexibility: Today is possible to use > ApiExtractor in other projects to gather information about C++ files, but > his > was never made by anyone (at least anyone told us), maybe due to the fact > that > ApiExtractor requires a lot of things that only makes sense on "Binding > Generation World", because it's internals aren't documented enough, etc. > I guess the lack of examples of what ApiExtractor is able to produce is the main reason. I wouldn't close the door for ApiExtractor to be factored out into separate project if there will be any serious use cases for its usage. It is always nice to see clear component separation inside any tool-chain, and would be to reserve ability for Shiboken to expose ApiExtractor feature separately for experiments even if code bases are merged. But I guess experiments won't work, because ApiExtractor is library, not a program, and should be compiled, and it is not even a Python module. If that is it - then it explains a lot. -- anatoly t.
_______________________________________________ PySide mailing list PySide@lists.pyside.org http://lists.pyside.org/listinfo/pyside
