GNOME Bugzilla – Bug 483840
Use .vapi as file extension for bindings
Last modified: 2007-10-08 19:26:42 UTC
We should probably use a separate file extension for VAPI files. This would allow us to pass local bindings just like source files on the command-line without --vapidir option or resorting to special attributes. It also helps to split bindings with custom vala code into a .vapi and a .vala file. Marking as blocker as we want breaking changes in a release as early as possible.
Sounds resonable to me. I think vapi files and vala files should be understood similar to source and header files in C. The syntax in those files is the same and the code could be distributed in different way (not every distribution would make sense though). This is pretty similar (apart that implementaiton code is ommited for now in vapi files) in vala. Question remains whether we want to state vapi files like source files or reference them in some other way (like in C through "#include"). It is IMO uncommon to state "header" and "source" on the same command line. e.g. in C you also state the includedir (similar to the vapidir in vala). However, only with requiering vapi files shall have a .vapi ending we do not enforce them beeing stated on the command line instead referenced through vapidir.
2007-10-08 Jürg Billeter <j@bitron.ch> * vala/valaparser.vala, compiler/valacompiler.vala: use .vapi as file extension for bindings, fixes bug 483840