[email protected] wrote:
> On 03/12/10 17:57, Greg Ercolano wrote:
>> (It's a weird programming tick I have when typing switch() and
>> esp. return(), but not with if or for.. not sure why)
>
> Hmm, I guess I'm more the other way - I always get the space after
> switch, but seem to leave it out after if() and for().
I know my typing muscles have a coding style all their own
when it comes to spaces. And unfortunately, I know the tule
varies in some cases, like spaces between comma separated args..
sometimes I space em, sometimes I don't. :/
> And I never use the braces after return... (Well, unless the return
> value actually has to be evaluated, and maybe not even then...)
Heh, I've always used parens after a return cause all the
other "action oriented" keywords that take parameters
seem to use them (switch/while/for/if/func).
return seems the odd one that doesn't require parens.
To me, without the parens it looks like a variable declaration, lol.
Agree, doesn't seem necessary to cover return in the CMP.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
