November 06, 2022 Re: Is D really that bad? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | On 06.11.22 05:53, Walter Bright wrote:
> On 11/5/2022 9:52 AM, razyk wrote:
>> FWIW Delphi added "strict private" and "strict protected".
>
> D will go one better:
>
> "private IReallyMeanItThisTime"
It was "Delphi 7" before.
|
November 06, 2022 Re: Is D really that bad? | ||||
---|---|---|---|---|
| ||||
Posted in reply to razyk | On Saturday, 5 November 2022 at 16:52:57 UTC, razyk wrote:
>
> FWIW Delphi added "strict private" and "strict protected".
Nice!
Honestly, I don't care much. I would prefer "private" to consistently mean "private to this scope". Given that languages like Python are doing well without any access attributes, we could just leave it as is.
|
November 08, 2022 Re: Is D really that bad? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | On Sunday, 6 November 2022 at 01:56:34 UTC, Walter Bright wrote:
> Divorcing modules from file names makes for clumsy, hackish attempts solutions to figuring out which file a particular module resides in.
Perl modules make for a good compromise -- when a module needs to be found, it's a 1:1 correlation to filename, but for modules referred to within the file, there is no such requirement.
That having been said, I can count on my fingers the number of times I've actually used multiple modules per file, and won't miss them writing D.
|
November 08, 2022 Re: Is D really that bad? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | On Sunday, 6 November 2022 at 01:56:34 UTC, Walter Bright wrote:
> Divorcing modules from file names makes for clumsy, hackish attempts solutions to figuring out which file a particular module resides in.
That is why build systems such as makefile exist for a very good reason. Even the C# requires the project solution.
- Alex
|
Copyright © 1999-2021 by the D Language Foundation