`restricted` member variables
Ola Fosheim Grøstad
ola.fosheim.grostad at gmail.com
Thu Jun 23 10:12:51 UTC 2022
On Thursday, 23 June 2022 at 09:49:25 UTC, Dom Disc wrote:
> No, but this whole discussion is only about coding style
> (putting each class in its own module or not). And from style
> guide perspective having more options is always bad. It reduces
> the readability.
From a readability perspective and an educational cost
perspective having «private» mean anything but the conventional
class-private is a mistake. So that has clearly not been the main
consideration when landing on the current setup. It is by and
large a personal opinion design. Much of the D design is
personal/opinionated.
Anyway, if you look at Phobos then you'll realize that the
language does not affect module structure to a significant
degree. Having more constraints, will not make people make create
more disorganized code. If anything you get more structure,
better documentation using language means and more opportunities
to clearly organize your code.
(But as noted before, this is not D's biggest issue…)
More information about the Digitalmars-d
mailing list