> From: "Peter Dimov" <[EMAIL PROTECTED]> > From: "William E. Kempf" <[EMAIL PROTECTED]> > > > From: "Peter Dimov" <[EMAIL PROTECTED]> > > > > > I think that a reasonable requirement that we already mentioned several > > > times is that the ID should be CopyConstructible, Assignable and > > > LessThanComparable, for use in sets/maps. > > > > Should it truly be LessThanComparable, or should it follow the design of > > std::type_info with a before() method? > > Something that meets the requirements stated above can be used in > > std::map<K, V>
You can do the same with std::type_info by supplying a template parameter other than the default std::less<>. I understand this need, and I understand how simple it is when you truly are LessThanComparable (and lean that direction myself). I just want to make sure that someone isn't going to argue that we should have followed the type_info design, since there's no true ordering for this type. William E. Kempf [EMAIL PROTECTED] _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
