Visual Basic ain't THAT bad
-
After three rum and cokes, some of the language choices seem to be not completely illogical. I'm sure when I come back to the macros I'm writing when completely sober tomorrow, VBA will make my eyes start bleeding again.
-
After three rum and cokes, some of the language choices seem to be not completely illogical. I'm sure when I come back to the macros I'm writing when completely sober tomorrow, VBA will make my eyes start bleeding again.
Dr. Plecostomus wrote:
when completely sober tomorrow
That's too early, uou wont be sober any time soon until the beginning of the new year
"Coming soon"
-
After three rum and cokes, some of the language choices seem to be not completely illogical. I'm sure when I come back to the macros I'm writing when completely sober tomorrow, VBA will make my eyes start bleeding again.
VB is in many ways far easier to read than C# - verbosity for the win. Using keywords helps map control structure end points back to their starting point without having to count braces. Where VB does fall flat on its face syntactically is writing LinQ queries.
-
VB is in many ways far easier to read than C# - verbosity for the win. Using keywords helps map control structure end points back to their starting point without having to count braces. Where VB does fall flat on its face syntactically is writing LinQ queries.
My favorite is CHILL (CCITT High Level Language) which allows you to label any block. The block is enclosed in braces, and between the closing brace and the semicolon, you may optionally repeat the label. If it doesn't match the label of the block, the compiler will produce an error message. Using the labels is optional; for tiny blocks you can use the braces only, for compact code. A label can be made far more descriptive than just identifying the kind of block. And the label is useful for flow control: You can directly leave an outer block from an inner block (possibly in multiple levels) by specifying the label of the block you want to leave; yo don't have to do it level by level (which probably requires a mess of variable flags for getting past the iteration control at the intermediate levels). In the C family, when a loop/if exceeds 10-12 lines I have made it a habit to repeat the if, while or for condition at the closing of the statement as an end-of-line comment, to get a CHILL-style readability improvement, but I can't make the compiler produce a warning/error if I do not make the nesting right.
Religious freedom is the freedom to say that two plus two make five.
-
After three rum and cokes, some of the language choices seem to be not completely illogical. I'm sure when I come back to the macros I'm writing when completely sober tomorrow, VBA will make my eyes start bleeding again.
The bad thing about Visual Basic is that it strays from actual BASIC too much. Panders to the least-skilled developers.