Quote:Original post by Grafalgar
However, that not being the case, I find it very difficult to adopt (and read) a convention that asks me to remember that indentation starts scope, but an ending brace with one less indentation ends it. That, to me, is not a very logical 'pairing' of functionality, ie they are not complementary.

Quote:
Compare to Python where the rule says indentation increase enters a new scope, indentation decrease exits scope. C++'s syntax, of course, enters a new scope with {, and exits it with }, and so I expect to see them used in the same way, however you define that to be.

Quote:Original post by Zahlman
Ah, well you see, I don't consider the braces to be part of the scope, in much the same way that I don't consider quotation marks to be part of a quotation. So to me, the convention simply asks you to remember that indentation denotes the contents of a scope - and that's the same whether you give the opening brace a new line or not.

Quote:
"used in the same way"? I can't extract any sense out of this argument; you seem to be saying that in either case, you should do what the language requires you to do. Well, duh.

Quote:Original post by CowboyNealFor example, sometimes you want to know if a String is an unsafe string or safe string. They are both type String, compiler will not help you out and Intellisense won't either, but that information can be very useful to know.

class SafeString {    public string Value { get; private set; }    public SafeString (string safeStringValue)    {        Value = stringValue;    }}class UnsafeString{   public string Value { get; private set; }    public SafeString (string unsafeStringValue)    {        Value = unsafeStringValue;    }}public void ProcessString(SafeString input){    //do something}public void Foo(UnsafeString input){    ProcessString(input); //error}

Quote:Original post by phresnel
Oh that is the pest in version control

Quote:Original post by DevFred

Quote:Original post by phresnel
Oh that is the pest in version control

Why does version control consider whitespace? Wouldn't it make more sense to be token-based, except for comments? I understand the version control would then need to know the language, but still... would seem like a great feature to me.