The future of C# and Visual Basic [video]

Re:The future of C# and Visual Basic [video] by moron4hire on Monday November 03, 2014 @10:39AM (#8551287)

Because a property is actually a method, so other, internal state could change what the property returns. Think of something like an "IsConnectionOpen" flag. The class' internals may change it as if it is not readonly, but to the consuming code, the IsConnectionOpen property should appear readonly.

[ Parent | on HN ]

Re:The future of C# and Visual Basic [video] by andrea_s on Monday November 03, 2014 @10:41AM (#8551298)

That's clear - but that's not the case presented in the slides...

"Automatic" is clear, "getter-only" is clear, but "automatic getter-only" leaves me scratching my head.

[ Parent | on HN ]

Re:The future of C# and Visual Basic [video] by moron4hire on Monday November 03, 2014 @10:51AM (#8551367)

Do you know where it is in the video? Are they not talking about something like this?

    public bool IsOpen{get; private set;}
    public void Open(){
        try{
            // do some complex work
            this.IsOpen = true;
        }
        catch{
            this.IsOpen = false;
        }
    }
    public void Close(){
        // do some other work
        this.IsOpen = false;
    }

[ Parent | on HN ]

Re:The future of C# and Visual Basic [video] by andrea_s on Monday November 03, 2014 @11:12AM (#8551524)

Not sure about the minute, the video is prohibitively long...

It's on the 9th slide: https://view.officeapps.live.com/op/view.aspx?src=http%3a%2f...

[ Parent | on HN ]

Re:The future of C# and Visual Basic [video] by moron4hire on Wednesday November 05, 2014 @10:43AM (#8562288)

I see. Maybe they mean "implicit private set"? Otherwise, one of the sibling comments has a good point about the binary compatibility issues with fields vs properties.

[ Parent | on HN ]