|
> From: Joel Fritz > > This is a style issue, and I think you're going to get some argument. <g> See my reply to Carel. You may think it's a style issue, I don't. Bad coding is not "style", it's just bad programming. But we can agree to disagree. > In my first C class in junior college, the instructor gave us expressions > like this to evaluate on tests. When I asked him about some of the > convoluted stuff (much more obscure than these loop control statements) he > threw at us he said something to the effect that a lot of people > write code > like this and you'll lose if you can't read it. He especially > liked things > that combined multiple levels of indirection with blurring the distinction > between logic and arithmetic. Your instructor was an idiot. > As a matter of personal taste, I don't care to write code like that, but I > can understand how someone would. I don't think it usually has anything to > do with job security--just a desire to cram as much as possible into as > little space as you can. I dinged people on their performance reviews if they insisted on coding that way. There is no place for it in a business environment. You want to code like that, do it at home. Joe "Doesn't Feel Like Beating Around the Bush" Pluta
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.