Warren Levy <[EMAIL PROTECTED]> writes: > Hmm, it looks to me like libgcj is using the same code for lookup as > classpath is (and has used for quite a while). Is this a change you think > applies to classpath also or did you think it was libgcj-specific? It applies to both. I don't see a reason for the two implementations in libgcj/classpath to diverge. We should probably lean towards the libgcj implementation... I especially like to remove our use of native methods unless they are really ncessary. Brian -- Brian Jones <[EMAIL PROTECTED]>
- Re: Utility for checking API compatibility with JDK Stuart Ballard
- Re: Utility for checking API compatibility with JDK Brian Jones
- Re: Utility for checking API compatibility with JDK Brian Jones
- Re: Utility for checking API compatibility with JDK Tom Tromey
- Re: Utility for checking API compatibility with JDK Brian Jones
- Re: Utility for checking API compatibility with JDK Stuart Ballard
- Re: Utility for checking API compatibility with JDK Warren Levy
- Re: Utility for checking API compatibility with JDK Warren Levy
- Re: Utility for checking API compatibility with JDK Warren Levy
- Re: Utility for checking API compatibility with JDK Warren Levy
- Re: Utility for checking API compatibility with JDK Jochen Hoenicke

