https://bugzilla.novell.com/show_bug.cgi?id=355255
User dmacvicar@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355255#c8
Duncan Mac-Vicar changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|sh@novell.com |dmacvicar@novell.com
Status|NEW |ASSIGNED
--- Comment #8 from Duncan Mac-Vicar 2008-03-11 08:44:48 MST ---
I think comment #6 is wrong.
APIs generally define the < operator as they go higher on the abstraction by
keeping the lower layers semantics.
For example, if you have a class person, you will probably define the <
operator based on the < operator on the name or the age, _without_ altering the
semantic of those operators, and it is the UI which defines a sort policy
_based_ (which means it could be the same) on the classes operators.
Almost every model controller architecture (including Qt's one) have hooks to
define the sort order because the "mathematic" sort order of the frameworks not
always is what you want to display to the user.
Usually changing the semantics of this means adding a one character to invert
the logic, or an if to exclude some items. Is that a problem?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.