Hi Jim, Well, the hole issue of programming standards and formatting in particular has to deal with a business model approach to programming. That is if you develop software for a company you and your coworkers can all develop software in the same way, use the same standards, and it makes it easier for everyone on the team to read code they themselves did not write. Plus as you said if you are fired, quit, or need to be replaced by someone else you can because the person replacing you will be able to read and understand the code based on the standards that were set by the lead developers.
Formatting is primarily there for sighted computer programmers. They can glance at the screen and see in an instance what scope a block of code is in because global scope is not indented where inner scope is indented according to the level of scope. For us, we can't see it, so unless we are following along with a braille display or have something like NVDA announce the number of indentions there is little use for us to format the code for our own personal use. Unless of course a blind developer is aiming for pro standards. Which brings us to your point. You said you can go back and read code you wrote decades ago. Of course, because you wrote it and it follows your own programming style and standards. That's fine if you are the only person to ever read it, but if another VB dev comes along and tries to update your game he or she might wonder what does this variable ab mean, and what data type is it? If it isn't properly formatted a sighted programmer won't even know what scope it belongs to without reading your entire program. Obviously, that's ok for private/personal software, but doesn't work in a business environment where everything has to be explained. If you have to be reassigned or replaced then the next programmer to step in and upgrade your code is going to be miserable if you used some shorthand that is known to you and nobody else. :D Cheers! On 2/16/12, Jim Kitchen <j...@kitchensinc.net> wrote: > Hi Trouble, > > Yeah, I was told a long time ago that the only reason they want business > standard code is so that you can be replaced. Personally I can go back to > code I wrote decades ago and still know exactly what I was doing. But I do > know that my code is not for others. I mean the first computer that I had > you could only use two letter variable names. I still do that all the time. > Now if I wanted others to be able to understand and change my code I should > use descriptive variable names and line labels. And VB6 doesn't make you > use any indenting format or anything like that. It does though in the IDE > speak your line and column if you turn on say all in Jaws. I don't though > as it is not needed. > > BFN > > Jim > > I like Visual Basic 6.0 because I can not C. > --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gamers@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
