On Fri, Feb 20, 2009 at 6:37 PM, Richard Dale <[email protected]>wrote:
<snip>
> It is a common misconception that a C api is easier to write language
> bindings against than a C++ api. However, I personally think we can get
> better results using C++ apis as a basis as long as they are not too heavy
> on templates (like boost for instance). Qt-like apis, such as Wt map very
> nicely onto other languages.
>
>
>>
>>
>> I was also wondering did wtRuby automate the process of binding to the Wt
>> API?
>> If so using which tools?
>>
> Yes, the process is pretty much entirely automatic, working like a C++ to
> language bindings library compiler. The compiler happens to be written in
> Perl, but it is complete enough to cope with large complex C++ apis such as
> Qt, KDE and Wt. The autogenerated 'Smoke library' for Wt and Wt::Ext is also
> language independent and could be used as a basic for other languages like
> C#, Perl or PHP and not just Ruby.
>
Thanks Richard.
I have no experience with automatically generated bindings. I assumed C
bindings would probably be required.
Just did some Googling and read a bit about SWIG and Smoke.
I guess I will download wtRuby to see how you taught Smoke to generate the
bindings for wtRuby.
Thanks,
Kind regards,
Maurice
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
