Hi all,
Currently Vala uses
- 'public' classes for classes that end up in the headers /and/ in the
library (if you're building one)
- 'private' classes for classes that don't end up in neither headers
/nor/ in the created libraries.
This means that you library will (usually) /export all your plumbing
classes/ to the world.
What would you think about using 'protected' (or 'internal') for types
that are present in header files (thus can be used inside the same
compilation unit) but that are /not exported in the library/?
With proper autotools configuration the header won't end up in the 'make
dist' either.
What do you think?
Is there already a solution I am overlooking?
Vlad
_______________________________________________
Vala-list mailing list
Vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list