Standardized Programming

Miscellaneous Forums/General Discussion/Standardized Programming

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

*lol*
Yeah CS_TBL, thats actually the best one ... don't show it off then it can't be wrong ;-)


I don't add the type to the variable. If I want to know it I just say: get Blide or ask yourself what type it holds ;-)
No in the end I know what it holds.
My vars are normally camel case (I was teached the multi word underline stuff by bertrand meyer in SE but I don't agree that this stuff is of any real readability) and I use different prefixes:

c: Constant
m: member, not meant to be used from outside
s: static / shared
sm: static member
T: for classes
S: Singleton classes
F: Factory classes

No all caps for constants, although I agree up to some point that it makes it easy to directly realize that it is a const. But it breaks the visual consistency of the code for me, thus c

Most BM users tend to use _ instead of m but I learned that this _ can easily be missed depending on the screen resolution and color settings so I dropped it again.

Beside that, I used to use the generala intend (example 3 of FDs assignement examples) but switched back to space = space again as it got really unreadable with different lengths of variables etc.