On 1. Oktober 2013 at 15:44:30, Alan Bateman (alan.bate...@oracle.com) wrote:
On 01/10/2013 01:50, Jörn Huxhorn wrote:
…just saying…
We know. It seems unlikely that there will be agreement on a standard
API or that there is time for a new API to bake. So the safest thing
might be just restore
On 01/10/2013 01:50, Jörn Huxhorn wrote:
…just saying…
We know. It seems unlikely that there will be agreement on a standard
API or that there is time for a new API to bake. So the safest thing
might be just restore the totally unsupported getCallerClass and submit
a JEP with a proposal to
On 01/10/2013 9:40 AM, Alan Bateman wrote:
On 01/10/2013 01:50, Jörn Huxhorn wrote:
…just saying…
We know. It seems unlikely that there will be agreement on a standard
API or that there is time for a new API to bake. So the safest thing
might be just restore the totally unsupported
2013/10/1 2:12 -0700, cow...@bbs.darktech.org:
Two questions:
1. restore the totally unsupported getCallerClass: Does that mean
it'll become supported again?
No. It never was supported. Use at your own risk.
2. submit a JEP with a proposal to add a standard API: Will this push