<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Le 17/10/14 02:00, Werner Keil a écrit :<br> <blockquote cite="mid: " type="cite"> <div dir="ltr">I see nothing that would break the Java language in either of the proposed approaches.</div> </blockquote> <br> <big><big><big><big>(...Sight...)</big></big></big></big> Werner, are you serious? Really?<br> <br> You leave me no choice. I will write to the OpenJDK list Sunday.<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr"> <p>I must disagree on that. The generic factory approach is incompatible with #1.</p> </div> </blockquote> I wrote that code years ago. You choose to delete it. I will bring it back.<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr">asType() has turned out to be unstable and cumbersome</div> </blockquote> You have never been able to give me any proof of that claim. I will never believe it without a code demonstrating the problem.<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr">Note, Otavio's suggestion goes pretty much in that direction<img src="cid:part1.00010309.09020602@geomatys.fr" goomoji="347" style="margin: 0px 0.2ex; vertical-align: middle;"></div> </blockquote> Otavio's suggestion is a violation of the Java language. The OpenJDK list reply (if they accept to reply) will make that clear.<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr">Including the problems with asType(). </div> </blockquote> I'm sure that this problem does not exist.<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr">If API insisted on a type like "Energy", then for each possible return type an interface and implementing class had to be declared</div> </blockquote> No Werner, I tried to explain you 4 times and you still do not understand me. The 50 currently existing interfaces, <b>one</b> <tt>java.lang.reflect.Proxy</tt> implementation, <b>nothing else needed</b> (but possible is some want optimizations).<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr">Both the Quantity<T> return type and a Quantity<?> one are flexible</div> </blockquote> They are unsafe.<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr">not forcing developers to declare an interface for every single final or intermediary value they need for their calculations.</div> </blockquote> No one suggested that, why are you still bringing that point?<br> <br> <br> <blockquote cite="mid: " type="cite"> <div dir="ltr"> <p>Otavio also mentioned, Lambda related JEPs including 101 could be broken or made extremely hard to cope with by the existing <?> approach.</p> </div> </blockquote> Okay, that is the first significant new point I have seen in this discussion for a while, thanks for bringing it. Can we have some details about this issue?<br> <br> <br> Martin<br> <br> </body> </html>
Attachment:
gifc_Y_9Puiaw.gif
Description: GIF image