Content deleted Content added
→C++: Pro 2 is only a pro in that wrapping can make the API OOP, where as C++ can call the C API as is. |
→Generated code?: revert |
||
Line 86:
:::::::I understand your point, but I still disagree. If x86 assembly language were widely used and well-known, it still wouldn't be very helpful in an article on Haskell, for example, to show the generated assembler code, since the aim of Haskell is not to produce assembly, but to generate binaries (i.e., generating assembly is just an implementation detail, or at best, a debugging aid). But in this case, the vala compiler is not just a front-end to a compiler, that just happens to generate C as an intermediate step in the compile process. It is a pre-processor with the stated goal of "[producing] C source and header files from Vala source files as if you've written your library or application directly in C", and the generated C is meant to be distributed to systems that don't host a vala compiler. If a specific focus of the project is to generate C source and headers, it makes sense to provide an example of the generated code, imo. [[Special:Contributions/24.243.3.27|24.243.3.27]] ([[User talk:24.243.3.27|talk]]) 05:58, 27 February 2009 (UTC)
:::::::Reverting to include generated C code per reasons given above. [[Special:Contributions/24.243.3.27|24.243.3.27]] ([[User talk:24.243.3.27|talk]]) 09:43, 1 March 2009 (UTC)
==Mem mgmt?==
| |||