• Create Account

### #Actualbrx

Posted 04 October 2012 - 02:00 PM

I don't like this

if(..) {
}

I prefer
if(..)
{
}


Been there... done it... got used it... makes no difference to me anymore...

I also don't like white space everywhere. Like

if ( bla ) {
do ( bla );
}


Yup, much nicer. [...]

Yes, I do agree, white spaces are YOUR FRIEND! However, liking this (i.e. the stated example
if ( s == o ) {
}

) is just WRONG! (ok, ok, it's all about opinions...) But, this is just something that *every single* coding convention I have ever used with agrees with (including the "official" Java and C# styleguides). The only people (at the place I work) that write like this are mathematicians that should not touch the code. PERIOD!!! (yes, I am getting carries away, but it's the truth!) It's got to look like this:
if (foo == bar) {
// there's what do do if foo equals bar
}

(and yes, I've seen very f'ed up coding conventions... ;) )

...

And, to stay on topic (although, I don't quite get it)... this is something evil to do:
#define TRUE FALSE //Happy debugging suckers

Some fun (most will already now it, but I like to read it once in a while): http://stackoverflow...ver-encountered

// way too many edits... time to go to bed...

### #6brx

Posted 04 October 2012 - 01:58 PM

I don't like this

if(..) {
}

I prefer
if(..)
{
}


Been there... done it... got used it... makes no difference to me anymore...

I also don't like white space everywhere. Like

if ( bla ) {
do ( bla );
}


Yup, much nicer. [...]

Yes, I do agree, white spaces are YOUR FRIEND! However, liking this (i.e. the stated example
if ( s == o ) {
}

) is just WRONG! (ok, ok, it's all about opinions...) But, this is just something that *every single* coding convention I have ever used with agrees with (including the "official" Java and C# styleguides). It's got to look like this:
if (foo == bar) {
// there's what do do if foo equals bar
}

(and yes, I've seen very f'ed up coding conventions... ;) )

...

And, to stay on topic (although, I don't quite get it)... this is something evil to do:
#define TRUE FALSE //Happy debugging suckers

Some fun (most will already now it, but I like to read it once in a while): http://stackoverflow...ver-encountered

// way too many edits... time to go to bed...

### #5brx

Posted 04 October 2012 - 01:56 PM

I don't like this

if(..) {
}

I prefer
if(..)
{
}


Been there... done it... got used it... makes no difference to me anymore...

I also don't like white space everywhere. Like

if ( bla ) {
do ( bla );
}


Yup, much nicer. [...]

Yes, I do agree, white spaces are YOUR FRIEND! However, not NOT liking the example stated (i.e.
if ( s == o ) {
}

) is just WRONG! (ok, ok, it's all about opinions...) But, this is just something that *every single* coding convention I have ever used with agrees with (including the "official" Java and C# styleguides). It's got to look like this:
if (foo == bar) {
// there's what do do if foo equals bar
}

(and yes, I've seen very f'ed up coding conventions... ;) )

...

And, to stay on topic (although, I don't quite get it)... this is something evil to do:
#define TRUE FALSE //Happy debugging suckers

Some fun (most will already now it, but I like to read it once in a while): http://stackoverflow...ver-encountered

// way too many edits... time to go to bed...

### #4brx

Posted 04 October 2012 - 01:54 PM

I don't like this

if(..) {
}

I prefer
if(..)
{
}


Been there... done it... got used it... makes no difference to me anymore...

I also don't like white space everywhere. Like

if ( bla ) {
do ( bla );
}


Yup, much nicer. [...]

Yes, I do agree, white spaces are YOUR FRIEND! However, not liking the example stated (i.e.
if ( s == o ) {
}

) is just WRONG! (ok, ok, it's all about opinions...) But, this is just something that *every single* coding convention I have ever used with agrees with (including the "official" Java and C# styleguides). It's got to look like this:
if (foo == bar) {
// there's what do do if foo equals bar
}

(and yes, I've seen very f'ed up coding conventions... ;) )

...

And, to stay on topic (although, I don't quite get it)... this is somthing evil to do:
#define TRUE FALSE //Happy debugging suckers

Some fun (most will already now it, but I like to read it once in a while): http://stackoverflow.com/questions/184618/what-is-the-best-comment-in-source-code-you-have-ever-encountered

### #3brx

Posted 04 October 2012 - 01:42 PM

I don't like this

if(..) {
}

I prefer
if(..)
{
}


Been there... done it... got used it... makes no difference to me anymore...

I also don't like white space everywhere. Like

if ( bla ) {
do ( bla );
}


Yup, much nicer. [...]

Yes, I do agree, white spaces are YOUR FRIEND! However, not liking the example stated (i.e.
if ( s == o ) {
}

) is just WRONG! (ok, ok, it's all about opinions...) But, this is just something that *every single* coding convention I have ever used with agrees with (including the "official" Java and C# styleguides). It's got to look like this:
if (foo == bar) {
// there's what do do if foo equals bar
}

(and yes, I've seen very f'ed up coding conventions... ;) )

### #2brx

Posted 04 October 2012 - 01:42 PM

I don't like this

if(..) {
}

I prefer
if(..)
{
}


Been there... done it... got used it... makes no difference to me anymore...

I also don't like white space everywhere. Like

if ( bla ) {
do ( bla );
}


Yup, much nicer. [...]

Yes, I do agree, white spaces are YOUR FRIEND! However, not liking the example stated (i.e.
if ( s == o ) {
}

) is just WRONG! (ok, ok, it's all about opinions...) But, this is just something that *every single* coding convention I have ever used with agrees with (including the "official" Java and C# styleguides). It's got to look like this:
if (foo == bar) {
// there's what do do if foo equals bar
}

(and yes, I've seen ver f'ed up coding conventions... ;) )

PARTNERS