EIFFEL VISITOR Sample Clauses

EIFFEL VISITOR. With the new functionality of the .NET parser (explicit interface member implementations, support of overloaded names) it was necessary to adapt the existing CW_EIFFEL_VISITOR. See section 2.2.3 for a short description of the Eiffel visitor. An AST node (CW_TYPE, CW_FUNCTION…) has a flag whether it was already visited through a visitor or not. (After the first visit, is_visited is true.) The Eiffel visitor is registered to every feature node type twice. In the non-visited state the features are either extended to creation_procedure_list (CW_CREATION_PROCEDURE_LIST) or feature_list (CW_FEATURE_LIST). Later, the visitor uses these two lists to generate an additional comment for overloaded features. In the actual visit where the visitor generates code for every node type, the visitor distinguishes between public and private features. The code of the feature body – the part between do and end – is only generated when the feature is public, otherwise the body remains empty. A private feature is an explicit interface member implementation of a type (see section 4.2.1). The generated source code of these features is not extended to the list containing procedures or features, but to the list interface_features. Finally, the source code that interface_features contains is written after the {NONE} clause of the current class text. To append the name of a feature to the class text, the visitor now uses overloaded_name instead of eiffel_name. Every feature node has an attribute overloaded_name, which is a unique name of the feature. When the original .NET method is not overloaded, overloaded_name is equal to eiffel_name. For all overloaded features generate_overloaded_comment comments the feature with additional information of the form -- (+2 overloads). This comment means that the class has two other features with the same Eiffel name. Now the creation_procedure_list and feature_list come into play since every feature is registered to one of them. A call of the form feature_list.overloaded_count (a_feature.eiffel_name) returns the number of features that have the same Eiffel name as a_feature. It works similarly with the creation procedures. Due to creation_procedure_list the code generation for the create clause implemented in generate_creation_text is also simplified. When is_by_reference of an argument type is true, the feature generate_feature_type sets type to the actual generic parameter of TYPED_POINTER [G]. The features generate_preconditions and generate_pos...
AutoNDA by SimpleDocs

Related to EIFFEL VISITOR

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.

  • SINGLE-USE PRODUCTS The Board of County Commissioners has established a single-use products and plastic bags policy intended to reduce the use of products which have become globally recognized as having lasting negative impacts on the environment. Neither single-use products nor plastic bags may be sold or disbursed on County property by staff or contracted vendors, except as set forth in Orange County Administrative Regulation 9.01.03. Failure to comply with the Regulation may result in termination of the contract or other contractual remedies, and may affect future contracting with the County. The use of reusable, recyclable, biodegradable, or compostable materials is encouraged.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Quality Improvement VRC shall develop programs designed to improve the quality of care provided by the Radiologists and encourage identification and adoption of best demonstrated processes. Practice and VRC acknowledge that, in connection with such quality improvement activities, it may be necessary to provide VRC with Protected Health Information and Practice and VRC agree to treat such information in accordance with Article 9;

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • School Improvement 1. The Board and the Association agree that employee participation in decision making is effective in providing positive results for education. 2. The provisions contained in this section shall apply to all school improvement plans, programs or processes set forth by school improvement committees established in the Xxxxxxx-Xxxxxx School District as a result of Section 1277 of the Revised School Code. 3. It is understood that participation on school improvement committees is voluntary. Further, employees who participate, or are non-participants, in such activities shall not be negatively evaluated for any conduct relative to such committees. 4. In the event that any provision(s) of a school improvement plan, program or process or application thereof violates, contradicts, or is inconsistent with this Collective Bargaining Agreement, the Collective Bargaining Agreement shall prevail.

  • Links to Third Party Sites/Third Party Services xxx.xxxxxxxxxxxxxxxxxx.xxx may contain links to other websites ("Linked Sites"). The Linked Sites are not under the control of Company and Company is not responsible for the contents of any Linked Site, including without limitation any link contained in a Linked Site, or any changes or updates to a Linked Site. Company is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Company of the site or any association with its operators. Certain services made available via xxx.xxxxxxxxxxxxxxxxxx.xxx are delivered by third party sites and organizations. By using any product, service or functionality originating from the xxx.xxxxxxxxxxxxxxxxxx.xxx domain, you hereby acknowledge and consent that Company may share such information and data with any third party with whom Company has a contractual relationship to provide the requested product, service or functionality on behalf of xxx.xxxxxxxxxxxxxxxxxx.xxx users and customers.

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