[Seta00]

Yes, I do, here's a sample:

PHP Code:

main() {
    new bar, baz = 29;

    for (new i = 0; i < baz; i++) {
        bar *= baz - i;
    }

    new arr[32];

    foo(bar, baz, arr, arr);
}

public foo(a, b, c[], d[32]) {
    assert((sizeof(c)-1) > 0);

    switch(a) {
        case 1: {
            b += 10;
        }

        case 2: {
            b += 13;
        }

        default: {
            b -= 2;
        }
    }

    if (b < 0) {
        b = abs(b) + a;
    } else {
        b -= a;
    }

    c[0] = a * b / (d[12] - d[10]);
    return d[31];
} 


To make it simple: I use K&R convention, with one exception: function's starting bracket in the same line of the function signature.

[joaquimandrade]

I'm with Bugsy on this but you two won't reach nothing with the discussion because none of the styles can be proved to be better.

[Bugsy]

if youre going to put the opening bracket on the same opening line why not put the closing bracket after the last line of code. consistency is what im getting at

[Seta00]

Originally Posted by Bugsy if youre going to put the opening bracket on the same opening line why not put the closing bracket after the last line of code. consistency is what im getting at

Originally Posted by Seta00 But, in the other hand, you can't predict when the code block will end, that's the reason to put the closing bracket alone in one line.

Readability before consistency.

[Bugsy]

lol not worth arguing with you. this is a matter of opinion.

[Seta00]

I know this discussion wont end, I'm just exposing my opinion over the tutorial. I think styling guidelines shouldn't be recommended, you just post links to all of them and let the programmer decide which one he will use.

[fysiks]

Originally Posted by Seta00 More code fitting in the page is for consistency, is way better to have functions that fit in one page, so you don't need to scroll up and down following the execution path.

lol

Originally Posted by Seta00 I think styling guidelines shouldn't be recommended

People can decide if they like the recommendation and choose to use or not use it.

[minimiller]

Originally Posted by Seta00 Nice tut, only thing I disagree is with the new line before opening bracket. If you're a programmer, you can easily recognize identifiers that imply a code block, and the new lines before every block allow for less code to fit in one page.

wtf pages!?!
u using ms word or some shit?

[Bugsy]

Originally Posted by minimiller wtf pages!?! u using ms word or some shit?

Seriously... I don't think "number of lines you can see on a page" should be a deciding factor for the format of code.

[ehha]

Originally Posted by Bugsy PHP Code: public Ugly( id ) { } public Nice( id ) { }

Here's why I agree on this, if you wanna do a quick eye search on a code block, it's just* a vertical swoop & you're done.

*and it looks better