<div dir="ltr">On 16 October 2013 10:53, Gabriel Dos Reis <span dir="ltr"><<a href="mailto:gdr@axiomatics.org" target="_blank">gdr@axiomatics.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Ville Voutilainen <<a href="mailto:ville.voutilainen@gmail.com">ville.voutilainen@gmail.com</a>> writes:<br>
<br>
| On 16 October 2013 18:46, Gabriel Dos Reis <<a href="mailto:gdr@axiomatics.org">gdr@axiomatics.org</a>> wrote:<br>
|<br>
|<br>
| | My own personal view (not that of chair) is that if std::less<T>(l,r)<br>
| and<br>
| | "l < r" are<br>
| | both defined, then they should yield the same answer.<br>
| |<br>
| |<br>
| | Which fails for pointers.<br>
|<br>
| "fails" in which sense? It is certainly true in the current standards<br>
| these expressions are both defined when 'l' and 'r' are related<br>
| addresses (relative to the same object), which was exactly my point.<br>
|<br>
| Fails in the sense that less<int*>(l, r) and l<r do not necessarily yield the<br>
| same answer.<br>
<br>
</div></div>Only on the cases, e.g. input values, where they aren't both defined.<br></blockquote><div><br></div><div>Only because they have different preconditions. They shouldn't.<br></div></div>-- <br> Nevin ":-)" Liber <mailto:<a href="mailto:nevin@eviloverlord.com" target="_blank">nevin@eviloverlord.com</a>> (847) 691-1404
</div></div>