Humans should think of sizeof() as a function, says Linus Torvalds

Post by skue » Sat, May 30, 2015, 4:10 PM UTC

rhaps0dy wrote: post #87

bigtunacan wrote: post #64

Earlier quoted context omitted.

We would all be better off if semi colons had just been required in JavaScript. The problem is that semi colons are not actually optional in JavaScript. Instead JavaScript use ASI, automatic semi colon invasion, where the compiler attempts to determine where semi colons should go. Unfortunately the rules are complex, prone to certain errors, and I can't rely on everyone I ever work with understanding all of those rul…

http://blog.izs.me/post/2353458699/an-open-letter-to-javascr... Please stop spreading FUD.

Post by Chathamization » Sat, May 30, 2015, 4:20 PM UTC

Post by csixty4 » Sat, May 30, 2015, 4:20 PM UTC

JoeAltmaier wrote: post #98

Igglyboo wrote: post #97

Earlier quoted context omitted.

The only problem with this is if/when someone comes along and doesn't notice the missing braces and does if (condition) Foo(x) Bar(x) Expecting Bar(x) to be part of the conditional. This can and does happen.

I hear folks say that, but don't encounter it in the wild. Maybe once in 20 years so far. That construct, reading it just now, just screams out at me "Indentation error!" Anyway it nicely illustrates the need to get braces out of there altogether. The programmers' intent is obvious; let the IDE 'make it so' by emitting braces in the generated code.

Post by jotux » Sat, May 30, 2015, 4:23 PM UTC

JoeAltmaier wrote: post #98

Igglyboo wrote: post #97

Earlier quoted context omitted.

The only problem with this is if/when someone comes along and doesn't notice the missing braces and does if (condition) Foo(x) Bar(x) Expecting Bar(x) to be part of the conditional. This can and does happen.

I hear folks say that, but don't encounter it in the wild. Maybe once in 20 years so far. That construct, reading it just now, just screams out at me "Indentation error!" Anyway it nicely illustrates the need to get braces out of there altogether. The programmers' intent is obvious; let the IDE 'make it so' by emitting braces in the generated code.

    if (condition)
        Foo(x);
        Bar(x);

    if(condition1)
        if(condition2)
            if(condition3 && condition4)
                Foo();

    if(condition1)
    {
        if(condition2)
        {
            if(condition3 && condition4)
            {
                Foo();
            }
        }
    }

    if (condition)
        Foo(x);

    if (condition)
    {
        Foo(x);
        Bar();
    }

Post by gumby » Sat, May 30, 2015, 4:40 PM UTC

barrkel wrote: post #31

krylon wrote: post #6

IIRC, if the argument to sizeof is a type, the parentheses are mandatory, anyway, so using it like it was a function is more consistent. I think the reason it is not a function from the standard's point of view is that C does not have any builtin functions (unless my memory totally fails me in this case), all functions have to be either defined locally or #included.

Another oddity of C that amuses me is the do/while loop without braces: int i = 4; do printf("hey\n"); while (--i > 0); Even though do/while is a keyword bracketing pair in C, it still only lets you use a single statement (because nested whiles). So everybody uses braces, and thus it looks quite disturbing without them.

    int i = 4;
    do
       printf("hey"), printf("Jude.\n");
    while (--i > 0);