Well...Visual Basic versions prior to the .Net releases contained a setting that allowed you to programmatically set the lower bound for arrays. You could choose 0 or 1 as the lowest bound so perhaps this guy is just an old school VB programmer who used OPTION BASE 1, but that's still retarded. In my many years of pre-.Net VB programming I only encountered one other programmer using this feature but it was for a legitimate use as it was part of a legacy mainframe interface program that had records starting at 1.
My current project is written in a Pascal-like language so I've started all my arrays at 1. It took some getting used to but it has its upsides... hey why are you looking at me like that? :P
6 comments
2 u/yhsvghnrOruGnpverzN 09 Jul 2017 22:52
This is the sort of content /v/programming wants? Fuck. I'm out.
2 u/Philosopher_King [OP] 10 Jul 2017 02:32
I would've posted it to v/Funny, but I honestly didn't think most people would understand the joke.
0 u/McBiscuit_PdH 10 Jul 2017 15:36
Not likely. And the explanation would probably seem like a semantic difference.
1 u/ditch-digger 09 Jul 2017 23:32
Was surfing All. Thought this was odd for v/funny, that nobody else would get it.
0 u/Morbo 10 Jul 2017 04:40
Well...Visual Basic versions prior to the .Net releases contained a setting that allowed you to programmatically set the lower bound for arrays. You could choose 0 or 1 as the lowest bound so perhaps this guy is just an old school VB programmer who used OPTION BASE 1, but that's still retarded. In my many years of pre-.Net VB programming I only encountered one other programmer using this feature but it was for a legitimate use as it was part of a legacy mainframe interface program that had records starting at 1.
VB/VBA Option Base Statement
0 u/tame 12 Jul 2017 23:31
My current project is written in a Pascal-like language so I've started all my arrays at 1. It took some getting used to but it has its upsides... hey why are you looking at me like that? :P