[gtkmm] PropertyProxies vs get/set?

[Mike Hearn <mike theoretic com>]

Hi,

I have a feeling this might be an FAQ, but hey, it's not actually in the
FAQ so it must be OK to ask, right? :)

I'd like to know why GTKmm apparently relegates PropertyProxies to a minor
implementation detail, and favours accessor methods instead. Coming from a
Delphi background, it seems natural to me to write code like this:

	tree.reorderable = true;

rather than

	tree.set_reorderable(true);

I wouldn't really mind get/setters if the propertyproxies were actually
named after the properties and documented, but it seems that instead all
the documentation is attached to the accessors instead and propertyproxies
need a slightly ugly property_ prefix.

I'm curious as to the reasoning behind this. I can understand having
accessors for those who prefer them - matter of taste - but it seems these
are the official GTKmm way and the ability to treat properties syntax-wise
as variables isn't used. Why not?

thanks -mike