Menu
Search

Forums

Forum Index

Thread overview
D Community Conversations: Walter Bright on the Origins of D Part 2
Oct 10, 2022
Mike Parker
Oct 13, 2022
Ali Çehreli
Oct 13, 2022
Dave P.
October 10, 2022
Gravatar of Mike ParkerPosted by Mike ParkerReply
Mike Parker
Gravatar of Mike Parker


Reply

Walter sat down with me over Jitsi Meet a couple of weeks ago for the second part of our conversation about the origins of D.

Part One covered the years before D and how they impacted the development of D, from his early inspiration for the game 'Empire', through his college years, his time at Boeing, and his career as a compiler developer. If you missed it, you can see it here:

https://youtu.be/-kkMYJN3MnA

In Part Two, we talk about some of his early design decisions, including a few hits and misses, and some of his thoughts behind them. Why did he change his mind on adding templates and operator overloading? What's the story with the strict class struct dichotomy? That and more are all right here:

https://youtu.be/G6b62HmsO6M

There's more I would have loved to have talked to him about, but I'll be able to get to some of it in a future conversation somewhere down the road. Before then, I have plans to drag someone else onto Jitsi with me for the next conversation. I have a list of people to pounce on, and the first one to accept will be my next guest.

October 13, 2022
Gravatar of ItIsEncapsulatedOrItisNotPosted by ItIsEncapsulatedOrItisNot
in reply to Mike Parker		Reply
ItIsEncapsulatedOrItisNot
Gravatar of ItIsEncapsulatedOrItisNot
Posted in reply to Mike Parker


Reply

On Monday, 10 October 2022 at 07:16:22 UTC, Mike Parker wrote:

>

private to the module?

arggh@!!!!!FGFEETHH$%U$SHERRTT

October 13, 2022
Gravatar of Dave P.Posted by Dave P.
in reply to Mike Parker		Reply
Dave P.
Gravatar of Dave P.
Posted in reply to Mike Parker


Reply

On Monday, 10 October 2022 at 07:16:22 UTC, Mike Parker wrote:

>

Walter sat down with me over Jitsi Meet a couple of weeks ago for the second part of our conversation about the origins of D.
[...]

I enjoyed these talks!

October 13, 2022
Gravatar of ItIsEncapsulatedOrItisNotPosted by ItIsEncapsulatedOrItisNot
in reply to ItIsEncapsulatedOrItisNot		Reply
ItIsEncapsulatedOrItisNot
Gravatar of ItIsEncapsulatedOrItisNot
Posted in reply to ItIsEncapsulatedOrItisNot


Reply
On Thursday, 13 October 2022 at 00:46:09 UTC, ItIsEncapsulatedOrItisNot wrote:
> On Monday, 10 October 2022 at 07:16:22 UTC, Mike Parker wrote:
>>
>
> private to the module?
>
> arggh@!!!!!FGFEETHH$%U$SHERRTT

btw. The version of D that I program in, has BOTH private to the module AND private to the class.

The world did not collapse.

My programs are now clearer than ever, has less bugs, and still work, just fine.
October 12, 2022
Gravatar of Ali ÇehreliPosted by Ali Çehreli
in reply to ItIsEncapsulatedOrItisNot		Reply
Ali Çehreli
Gravatar of Ali Çehreli
Posted in reply to ItIsEncapsulatedOrItisNot


Reply
On 10/12/22 17:52, ItIsEncapsulatedOrItisNot wrote:
> On Thursday, 13 October 2022 at 00:46:09 UTC, ItIsEncapsulatedOrItisNot
> wrote:

Creative new name. However, although access rights are related to encapsulation, they don't provide it. Encapsulation is encapsulation.

> My programs are now clearer than ever, has less bugs, and still work,
> just fine.

If you removed all private keywords from your programs absolutely nothing would change.

Ali
October 14, 2022
Gravatar of ItIsEncapsulatedOrItisNotPosted by ItIsEncapsulatedOrItisNot
in reply to Ali Çehreli		Reply
ItIsEncapsulatedOrItisNot
Gravatar of ItIsEncapsulatedOrItisNot
Posted in reply to Ali Çehreli


Reply
On Thursday, 13 October 2022 at 01:33:54 UTC, Ali Çehreli wrote:
> On 10/12/22 17:52, ItIsEncapsulatedOrItisNot wrote:
> > On Thursday, 13 October 2022 at 00:46:09 UTC,
> ItIsEncapsulatedOrItisNot
> > wrote:
>
> Creative new name. However, although access rights are related to encapsulation, they don't provide it. Encapsulation is encapsulation.
>
> > My programs are now clearer than ever, has less bugs, and
> still work,
> > just fine.
>
> If you removed all private keywords from your programs absolutely nothing would change.
>
> Ali

I don't think of 'private' as an 'access right'.

I think of it as a programmer assertion - in that it asserts the scope that I want to apply to that property of the class (and to which i expect the compiler to uphold that assertion).

Of course I don't need this in functions, since scope is always local to the function (except when its not).