Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
Ian Lance Taylor <[email protected]> Wed, 12 Aug 2015 09:24:06 -0700
| Newsgroups | gmane.comp.gcc.java.patches,gmane.comp.gcc.patches |
|---|---|
| Message-ID | <CAKOQZ8x03_3HwKc3Dm8qXyxnhnYezHidq88R+VMkL7T04OpPqg@mail.gmail.com> |
On Wed, Aug 12, 2015 at 9:21 AM, Tom Tromey <[email protected]> wrote: > Jeff> In the past this has stalled on issues like how will asynch-exceptions > Jeff> be tested and the like. > > It seems to me that either there is some other language which needs this > -- in which case that language ought to have testing for the feature -- > or the feature is only used by gcj, in which case it doesn't matter. > > Of course is!=ought; but relying on gcj and libjava to provide this > small amount of testing seems like a bad cost/benefit tradeoff. Go does use asynchronous exceptions, and has test cases that rely on them working. Ian