Re: Literate style, making code more readable or going overboard?

Hi all,

For me, negation becomes more confusing when the expression involves
relational and boolean operators. I know DeMorgan's theorem, of course, but
I don't wanna hafta think about it. And if the expression includes multiple
operators, parentheses, or unparenthesized precedence differences, I'm prone
to mistkaes.

I don't mind negating a simple predicate like isEmpty().

Still, it's too bad the list class lacks a hasItems() method.

Dale

-- 
Dale Emery
Consultant to software teams and leaders
Web: http://dhemery.com
Weblog: http://cwd.dhemery.com


[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/