I would disagree.
My brother in law has been programming for about 15 years most of that time was in C and C++. I remember having a similar discussion with him back about 1998 when I knew even less than I do now.
He told me that he could remember 2 separate occasions where programmers were fired for using ? : syntax. The reason being that it's just way too easy to introduce bugs as your eyes scan over the statment and you mis-interperet what it does.
The same thing rules applied for this sort of thing:
if (somevar) doSomething;
i.e.
if statements without the { }.In that case it's just way too easy to add a second statement before or after the first not realizing that the second one will be executed whether the if statment is true or not. That can lead to some horribly hard to find bugs.
All of this was part of the corporate coding standards at the companies where he worked, so anyone who did things differently would have been not only in the minority, but probably in need of work ;) These were some pretty large multinational companies like Phillips and JP Morgan, so I'd say they probably learned the hard way why it had to be done that way and that would be why they came down so heavily on people who refused to follow the standards.
Spike
Adam Cameron wrote:
I'm sure it'll surprise no one to learn that when I audited code and wrote coding standards for a living, I tended to recommend people avoid those operators? ;)
Things are beginning to become clearer for me, yes.
You would have found yourself in quite a small minority there, would you not? What's the rationale there then?
(Serious, non-atagonistic question)
Adam
--
-------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk
Do you cfeclipse? http://cfeclipse.tigris.org
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
