Linked by Quentin Hartman on Mon 14th Jul 2008 08:46 UTC, submitted by makkus
Thread beginning with comment 322859
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: private structure fields - Vala
by ebasconp on Mon 14th Jul 2008 17:44
in reply to "RE[3]: private structure fields - Vala"
RE[5]: private structure fields - Vala
by YEPHENAS on Mon 14th Jul 2008 18:07
in reply to "RE[4]: private structure fields - Vala"
So, do you think is feasible to write the new GTK+ stuff JUST in Vala?
Vala would be in charge of all the plumbing and the developer would not need about anything (that's the rational behind Vala, of course)
Vala would be in charge of all the plumbing and the developer would not need about anything (that's the rational behind Vala, of course)
Basically it should be possible, but Vala has still bugs and the syntax is still changing sometimes, it's not a final version yet. GTK developers would have to tightly cooperate with the Vala developers. But as I understand GTK+ 3.x is not intended as a complete rewrite, but as a major refactoring and extension. In my opinion it would be reasonable to implement new widgets and components in Vala and let the others be plain C until they get replaced at some time. GObject/C and Vala classes happily work together as they are the same.






Member since:
2008-07-14
What about written a real Vala compiler that receives as input a Vala source code and outputs a binary GTK+ compliant?
Would be possible, but the current solution with C as an intermediate language has the advantage that you get all C compiler optimizations for free. And it is possible to distribute the generated C source along with the source tarball. So if someone wants to compile the application for his platform he wouldn't even need the Vala compiler.
Using C as an intermediate language for compiling is not uncommon. For example Eiffel does this, too.
Actually it's GLib centric.