Consider removing the private access specifier

[JasperHorn]

Private is actually implemented as protected (the two are aliases in the datatype definitions at the moment). The reason for this is that private properties don't actually make sense, because the generated class does not actually use them. The only way to make use of them would be to have child class of the generated class and use them there. But that's protected, not private...

If it's not private, why call it that?

[JasperHorn]

Do we need access specifiers at all?

I don't really see much use for them, to be honest, and just removing them simplifies the datatype format (and the code used to parse it too, of course)

[JasperHorn]

I'm leaning more and more to removing all access specifiers. And the getters and setters right along with them (leaving us with only the __set/__get properties.