Object Contracts‌ Sample Clauses

Object Contracts‌. An object contract is a simple key/contract map. It is defined by a mapping from key values (which are either property names, array indices, or symbols) to contracts. Like a function contract, an object contract is delayed. All contracts in the mapping are dormant until the associated property is addressed by a property read or property write operation. When reading a property, the contract gets asserted to the accessed value before it is given to the context, whereas writing a property asserts the contract to the new value. The following example demonstrates the construction of an object contract that indicates that the length property of an object has to be a value of type "number". The constructor Contract.Object takes an enumerable JavaScript object (either an array or a normal object) that maps key values to contracts.
Sample 1
AutoNDA by SimpleDocs

Related to Object Contracts‌

  • Assumed Contracts The term "Assumed Contracts" shall have the meaning set forth in Section 2.1(e).

  • SUB-CONTRACTS (a) The Servicer may sub-contract or delegate the performance of all or any of its powers and obligations under this Agreement, provided that (but subject to Section 3.2(b)):

  • Material Contracts Section 3.20

  • Project contract 1. For each approved project a project contract shall be concluded between the Programme Operator and the Project Promoter.

  • Service Contracts (a) The Trustees may, at any time and from time to time, contract for exclusive or nonexclusive advisory, management and/or administrative services for the Trust or for any Series with any Person; and any such contract may contain such other terms as the Trustees may determine, including without limitation, authority for the Investment Adviser to determine from time to time without prior consultation with the Trustees what investments shall be purchased, held, sold or exchanged and what portion, if any, of the assets of the Trust shall be held uninvested and to make changes in the Trust's investments, and such other responsibilities as may specifically be delegated to such Person.

  • Covered Contracts and Contractors If the Contract exceeds $100,000 and the Contractor employed more than 40 full-time employees on a single working day during the previous 12 months in Minnesota or in the state where it has its principle place of business, then the Contractor must comply with the requirements of Minnesota Statute § 363A.36 and Minnesota Rule Parts 5000.3400-5000.3600. A Contractor covered by Minnesota Statute § 363A.36 because it employed more than 40 full-time employees in another state and does not have a certificate of compliance, must certify that it is in compliance with federal affirmative action requirements.

  • Existing Contracts Billing terms and provisions contained in existing contracting entity agreements (existing as of the date this policy is approved by the Board of Supervisors) shall remain in effect for the life of the contract. However, when these existing contracts are renegotiated, they shall contain the billing provisions as set forth in this policy.

  • Third Party Contracts From the Effective Date through and including the Closing Date, Seller agrees to enter into only those third-party contracts which are necessary to carry out its obligations under Section 5.2, which shall be on market terms and cancellable on thirty (30) days written notice or less, without payment of any fee or penalty. Copies of all such contracts so entered into by Seller shall be promptly provided by Seller to Purchaser.

  • Shared Contracts (a) Except as set forth on Schedule VIII, the Parties shall, and shall cause the members of their respective Groups to, use their respective reasonable best efforts to work together (and, if necessary and desirable, to work with the third party to such Shared Contract) in an effort to divide, partially assign, modify or replicate (in whole or in part) the respective rights and obligations under and in respect of any Shared Contract, such that (a) a member of the SpinCo Group is the beneficiary of the rights and is responsible for the obligations related to that portion of such Shared Contract relating to the SpinCo Business (the “SpinCo Portion”), which rights shall be a SpinCo Asset and which obligations shall be a SpinCo Liability, and (b) a member of the Nuance Group is the beneficiary of the rights and is responsible for the obligations related to such Shared Contract not relating to the SpinCo Business (the “Nuance Portion”), which rights shall be a Nuance Asset and which obligations shall be a Nuance Liability. Nothing in this Agreement shall require the division, partial assignment, modification or replication of a Shared Contract unless and until any necessary Consents are obtained or made, as applicable. If the Parties, or their respective Group members, as applicable, are not able to enter into an arrangement to formally divide, partially assign, modify or replicate such Shared Contract prior to the Distribution as contemplated by the previous sentence, then the Parties shall, and shall cause their respective Group members to, cooperate in any reasonable and permissible arrangement to provide that, following the Distribution, a member of the SpinCo Group shall receive the interest in the benefits and obligations of the SpinCo Portion under such Shared Contract and a member of the Nuance Group shall receive the interest in the benefits and obligations of the Nuance Portion under such Shared Contract, it being understood that no Party shall have Liability to the other Party for the failure of any third party to perform its obligations under any such Shared Contract.

  • Management Contracts The Recipient agrees that from the date hereof until the date on which none of the Infrastructure Bonds, of which the proceeds were used to pay or reimburse the costs of the Project, remain outstanding (the "Agreement Term"):

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!