Java Compatibility Sample Clauses

Java Compatibility. (i) Initially, the AAPI shall be that which is reflected in the Technology as identified in Exhibit A, by the bytecode specification in the Documentation entitled "Java Virtual Machine Specification" and by the Java language specification in the Documentation entitled "Java Language Specification." Subsequently, the AAPI may be modified by SUN and SUN will give Licensee written notice thereof. (ii) From time to time, SUN will make publicly available test suites at no cost for validating that the portion of Licensee's Product which interprets Java bytecodes complies with the then-current Specification of the AAPI as defined by SUN as of the date of that test suite ("Java Test Suite"). SUN shall not publish more than four (4) versions of such Java Test Suites in any one (1) calendar year, without the consent of Licensee, which consent shall not be unreasonably delayed or denied. SUN shall use reasonable efforts to review any changes to such Java Test Suites as much in advance as possible with Licensee, but failure of SUN to do so shall not constitute a breach of this Agreement and shall not invalidate any such Java Test Suite published by SUN. Changes to Java Test Suites to correct errors shall not be counted against the limitation to four (4). (iii) Each revision of a Product released by Licensee must pass the Java Test Suite that was current one hundred twenty (120) days before First Customer Shipment of such Product. Licensee shall not release or distribute to any third party the portion of Licensee's Product that interprets Java bytecodes, which does not successfully pass such Java Test Suite. (iv) If Licensee provides SUN with written notice of the existence of a bug in a current Java Test Suite, then Licensee shall be released from compatibility with the minimum portion of such Java Test Suite necessary to avoid the impact of such bug, until such time as Sun provides to Licensee a corrected or new Java Test Suite.
View SourceView Similar (3)
Java Compatibility. From time to time, Sun will make available test suites at no cost for validating that the portion of Licensee's Product which interprets Java bytecodes complies with the then-current AAPI as defined by Sun as of the date of that test suite ("Java Test Suite").
View Source
Java Compatibility. J&s is mostly backward-compatible with Java. Any Java code with no nested classes is also legal J&s code. J&s programs may use existing Java code, including libraries that are compiled by a Java compiler. Of course, precompiled Java code does not enjoy the benefit of class sharing. The J&s reference object forwards method calls to hashCode, equals, etc., and therefore J&s objects may be passed to Java code, for example, to be stored in a HashSet. There is one limitation in the current implementation: a J&s class cannot be shared if it inherits from any Java superclass other than java.lang.Object, or if it implements most Java interfaces. This is the artifact of using reference objects to support views; a lower- level implementation should not have this limitation.
View Source
Java Compatibility. J&s is mostly backward-compatible with Java. Any Java code with no nested classes is also legal J&s code. J&s programs may use existing Java code, including libraries that are compiled by a Java compiler. Of course, precompiled Java code does not enjoy the benefit of class sharing. The J&s reference object forwards method calls to hashCode, equals, etc., and therefore J&s objects may base Exp Exp sum Exp Pair Abs Abs Case sumpair Exp Pair Abs Case be passed to Java code, for example, to be stored in a HashSet. There is one limitation in the current implementation: a J&s class cannot be shared if it inherits from any Java superclass other than java.lang.Object, or if it implements most Java interfaces. This is the artifact of using reference objects to support views; a lower- level implementation should not have this limitation. The J&s language currently extends Java 1.4. It does not support generics, which seem to be an orthogonal feature. We leave the interaction between generics and class sharing to future work.
View Source

Related to Java Compatibility

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Year 2000 Compatibility Take all actions necessary to assure the Borrower's computer based systems are able to operate and effectively process data on and after January 1, 2000. At the request of the Lender, the Borrower shall provide the Lender with assurance acceptable to the Lender that Borrower's computer systems have Year 2000 compatibility.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Industry Troubleshooter Where a difference arises between the parties relating to the dismissal, discipline, or suspension of an employee, or to the interpretation, application, operation, or alleged violation of this Agreement, including any question as to whether a matter is arbitrable, during the term of the Collective Agreement, ▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇, ▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇▇▇▇, or a substitute agreed to by the parties, shall at the request of either party:

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp.