Re: [Jython-dev] Java 7 or 8?
Jeff Allen <[email protected]> Sat, 10 Aug 2019 07:49:16 +0100
| Newsgroups | gmane.comp.lang.jython.user,gmane.comp.lang.jython.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============8117331690390252765==
Content-Type: multipart/alternative;
boundary="------------BCC41A074BC24DBE2B35BB1E"
Content-Language: en-GB
This is a multi-part message in MIME format.
--------------BCC41A074BC24DBE2B35BB1E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
On 27/07/2019 17:32, James Klo via Jython-users wrote:
> [snipped lots of other good points]
>
> Jeff mentions:
>>
>> We currently build and test
>> on Java 7 but some things would resolve themselves if we
>> could move on.
>>
>
> Could there be some elaboration here? What issues on the 2.7.2
> milestone would be solved by moving to J8? Pluses and minuses here
> would be helpful.
I was thinking of:
* https://bugs.jython.org/issue2770 (SSL test failures)
* I wrote a substitute base64 decoder in
https://bugs.jython.org/issue2663 (which was fun, but it could be
removed at Java 8).
* The odd place where a lambda would save nugatory work (logging).
Only the first is an actual problem for users (who have to downgrade
their JAR to match their insecure JVM). There may be other bugs we
didn't consider blockers that are also 7-isms.
Jeff
Jeff Allen
--------------BCC41A074BC24DBE2B35BB1E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 27/07/2019 17:32, James Klo via Jython-users wrote:<br>
<blockquote type="cite"
cite="mid:[email protected]">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
[snipped lots of other good points]
<div><br>
</div>
<div>Jeff mentions:</div>
<div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0px 0px 0px
0.8ex; border-left-color: rgb(204, 204, 204);
padding-left: 1ex;">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0px 0px
0px 0.8ex; border-left-color: rgb(204, 204, 204);
padding-left: 1ex;">
<font color="#000000"><span style="caret-color:
rgb(0, 0, 0); background-color: rgba(255, 255,
255, 0);">We currently build and test <br>
on Java 7 but some things would resolve
themselves if we could move on. </span></font></blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</div>
<div>Could there be some elaboration here? What issues on the
2.7.2 milestone would be solved by moving to J8? Pluses and
minuses here would be helpful. </div>
</blockquote>
<p>I was thinking of:</p>
<ul>
<li><a class="moz-txt-link-freetext" href="https://bugs.jython.org/issue2770">https://bugs.jython.org/issue2770</a> (SSL test failures)<br>
</li>
<li>I wrote a substitute base64 decoder in
<a class="moz-txt-link-freetext" href="https://bugs.jython.org/issue2663">https://bugs.jython.org/issue2663</a> (which was fun, but it could
be removed at Java 8).</li>
<li>The odd place where a lambda would save nugatory work
(logging).</li>
</ul>
<p>Only the first is an actual problem for users (who have to
downgrade their JAR to match their insecure JVM). There may be
other bugs we didn't consider blockers that are also 7-isms.<br>
</p>
Jeff
<pre class="moz-signature" cols="72">Jeff Allen
</pre>
</body>
</html>
--------------BCC41A074BC24DBE2B35BB1E--
--===============8117331690390252765==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============8117331690390252765==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Jython-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-users
--===============8117331690390252765==--