> > Of course, that does leave the question of how often you need one or the > other. Maybe just the asymmetric visibility is sufficient for most > practical purposes, in which case it may not be worthwhile to introduce > readonly properties as a separate feature. >
The examples shown in my previous email are indeed not very practical, but still, I would say that the added protection against possible misuse or accidental modifications (coming from either inside or outside) would be useful. Maybe it would make more sense to forbid readonly properties with default > values? > As I mentioned in my response to Larry, my point of view is that default values should be allowed. If there is a big opposition against this, I'm open for a change though. > Regarding the keyword choice, I think you can drop "sealed" from the list, > as it is an established term that affects inheritance, not mutability. Of > the choices you present, "immutable", "readonly" and "writeonce" seem like > the most viable candidates. > Thank you for the suggestions! Sure, we can drop "sealed", and I'm ok to add "immutable" and "readonly" to the list of voting choices. I'll also extend the evaluations with your thoughts. Regard, Máté
