Content deleted Content added
Line 40:
** I think it's worth pointing out that C++ can call the C libraries without any need to wrap the API in most cases. Vala just makes it easy to wrap the C API to fit into Vala's OOP style. [[User:Losinggeneration|Losinggeneration]] ([[User talk:Losinggeneration|talk]]) 10:01, 27 February 2009 (UTC)
*** You at least need to ''extern "C" {}'' the callee and include the C header. [[Special:Contributions/24.243.3.27|24.243.3.27]] ([[User talk:24.243.3.27|talk]]) 08:50, 24 March 2009 (UTC)
**** Still one of the big advantages of C++ is you can usuaully just include the C header in an extern "C" block (unless the C header trys to get really fancy). With most other languages you have to actually translate the imports (and home the library authors don't change them. [[User:Plugwash|Plugwash]] ([[User talk:Plugwash|talk]]) 19:46, 24 April 2009 (UTC)
* Vala also makes it easy to write C libraries -- you can use Vala to write libraries, compile them to C files, then distribute the C files. Vala can even generate a VAPI for the library along with the C files, so that you can use the compiled library from Vala -- i.e., you can use Vala to write a C library that can be used from any application with a C ABI and natively from Vala itself (the tutorial shows an example of this near the bottom).
* Since it is so tightly coupled with Glib/Gobject it obviously make it easier working with libraries that also use GLib/GObject.
| |||