Sealed classes - would you want them in D?

KingJoffrey KingJoffrey at KingJoffrey.com
Wed May 16 02:44:15 UTC 2018


On Tuesday, 15 May 2018 at 19:56:58 UTC, Patrick Schluter wrote:
> On Tuesday, 15 May 2018 at 02:32:05 UTC, KingJoffrey wrote:
>> On Tuesday, 15 May 2018 at 02:00:17 UTC, 12345swordy wrote:
>>> On Tuesday, 15 May 2018 at 00:28:42 UTC, KingJoffrey wrote:
>>>> On Monday, 14 May 2018 at 19:40:18 UTC, 12345swordy wrote:
>>>>> [...]
>>>>
>>>> If 'getting a module to respect the enscapsulation 
>>>> boundaries the programmer puts in place would change the 
>>>> language so 'fundamentally', then the language 'already' 
>>>> presents big problems for large complex application 
>>>> development.
>>>>
>>> Evidence for this claim please.
>>
>> - Object independence
>> - Do not violate encapsulation
>> - Respect the interface
>>
>> All large software projects are done in (or moving toward) 
>> languages that respect these idioms.
>>
>> Those that don't, are the ones we typically have problems with.
>>
>> Isn't that evidence enough?
>
> That's not evidence, that's pure opinion. There's not a shred 
> of data in that list.

Actually, that is the history of the evolution of programming 
large, complex systems, that have to be to correct, safe, and 
amenable to change.

What other approach would work?



More information about the Digitalmars-d mailing list