Lou: @Waccoon
I wasn't trying to look cool by using b+=1 vs. b=b+1, just pointing out there's less chance of a logic error when the code is split up with one function per line. It's easier to debug.
Uh, you were actually comparing "+=" to "++".
C is perfectly capable of using "+=", which means your example effectively is C code. A better example would be nice.
Lou: I mean it's just a fugly language that makes for poor readability and prone to bad indexing, illegal referencing and logic errors.
Everyone knows these problems don't exist in non-C lanugage, of course.
As with most topics in this thread, you're trying too hard to defend or bash one particular way of doing things. You don't keep your options open, or even care to know about them.
Koaftder: yes, your {{{}}} example is cute
Indeed. Good programmers don't nest lots of loops. C also doesn't require code to be broken into blocks in most cases. Brackets are designed to improve readability, if used wisely.
Thus, the endless debate about whether to use open brackets at the end of a line or on a new line by itself. Personally, I prefer the end-of-line structure, but C doesn't force anyone to do that. That's what's nice about the structure of C code. For the most part, it doesn't dictate form, like many BASICs do.
Lou: /* let me count...did I use enough closing brackets? */
*cough* Try indenting, or at least use the "[ code]" tag when you want to show examples in a forum.
If you don't indent when using "THEN", "ELSE", and "END IF", does that improve readability?
Lou:
If ... THEN
I find keywords to be much harder to read than brackets, capitalized or not. But, that's just me.
Lou: Dim i as short
This is easier to read than "int i=0;"?
