Yo, thats nice! Iirc I've used PascalCase for my variables back then, and don't ask me whypic.twitter.com/MOSoYdkJw7
Upcoming episode of QB64 Report talks about coding styles, including variable naming conventions. How do you name your variables?pic.twitter.com/Fb5gzKUWUW
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
PascalCase
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
CamelCase for SUBs, Functions, Types, and exterior facing variables. Pot_Hole_Camel_Case for internal variables. I forget the correct terms, but if the variable gets trashed in the SUB then it has underscores in it, but variables the whole program uses have no holes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
PascalCase for generic variables, Camel_snake_case for anything mission critical. Alternatively peek and poke everything into video ram because it's free real estate.
- End of conversation
New conversation -
-
-
Back when I did (visual) basic stuff, I used PascalCase. Now I use various languages so I stick to the language's conventions
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Consistency is more important than the style itself.
-
Very much agreed!
End of conversation
New conversation -
-
-
Depends on where I'm coding. Try to stay on framework/language standard. When working with java: camelCase. When working with .net PascalCase. Other environments as C tends to be camelCase with variation.pic.twitter.com/NQwqw0XLyB
-
@ the gif!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.