FROM : Hamish Allan
DATE : Mon May 26 21:38:11 2008
On Mon, May 26, 2008 at 8:12 PM, Michael Gardner <<email_removed>> wrote:
> I disagree with the whole notion that using the result of an assignment
> is "bad style" or "confusing". I find it quite clear and natural to use
> constructs like "while (foo = [enumerator nextObject])", and I suggest
> to those who are uncomfortable with the similarity of the = and ==
> operators to use an editor that makes the difference clear, perhaps via
> syntax coloring. And adding extra parentheses just to assure the
> compiler that you know what you're doing is man serving machine, not the
> other way around as it should be.
Why tinker with syntax highlighting to make the difference a bit
clearer, when the compiler you're already using already makes the
difference crystal clear?
Presumably, using debugging tools is also a case of man serving
machine -- you should just write the code properly in the first place
;)
Hamish
DATE : Mon May 26 21:38:11 2008
On Mon, May 26, 2008 at 8:12 PM, Michael Gardner <<email_removed>> wrote:
> I disagree with the whole notion that using the result of an assignment
> is "bad style" or "confusing". I find it quite clear and natural to use
> constructs like "while (foo = [enumerator nextObject])", and I suggest
> to those who are uncomfortable with the similarity of the = and ==
> operators to use an editor that makes the difference clear, perhaps via
> syntax coloring. And adding extra parentheses just to assure the
> compiler that you know what you're doing is man serving machine, not the
> other way around as it should be.
Why tinker with syntax highlighting to make the difference a bit
clearer, when the compiler you're already using already makes the
difference crystal clear?
Presumably, using debugging tools is also a case of man serving
machine -- you should just write the code properly in the first place
;)
Hamish






Cocoa mail archive

