SYNTAX CHECK Sample Clauses

SYNTAX CHECK. Before the wizard compiles the generated Eiffel classes we wanted to check them for syntax errors. There were many approaches until we came up with the final solution. I will discuss them briefly. Our first idea was to use Gobo Eiffel Lint (gelint) [3]. Gelint is a tool which is able to analyze Eiffel source code and report validity errors. It uses the tools Gobo Eiffel Lex (gelex) and Gobo Eiffel Yacc (geyacc). Regrettably gelint only works on classic Eiffel, not on Eiffel for .NET. The problem is that the ISE Eiffel compiler relies on some XML files to make the correspondence between .NET and Eiffel for .NET classes; and this format is not published. The second approach was to implement an Eiffel assertion parser. I took the grammar description from the Gobo Eiffel Parse Library and swept everything out that is not needed to parse an assertion. The start condition was no more %start Class_declarations but %start Assertions. Then I used geyacc to generate an Eiffel assertion parser. Whenever the user added a new assertion (invariant, pre- or postcondition) the assembly dialog checks it using the assertion parser. A drawback of this approach is that the assertion grammar description of the yacc file has to be adapted manually when the Eiffel syntax changes so it does not come automatically with a new gobo release. However the assertion checker still exists and can be rebound in the wizard easily. I tried to come up with an algorithm that checks for validity of the assertion expression. I made a list of identifiers occurring in the assertion and checked if they match a feature name of the current class or a parameter of the feature in case of a pre- or postcondition. This approach was too restrictive: an identifier is also valid when it relies on a parent feature but then it got rejected. The next idea was to generate a second set of classes that only contains classic Eiffel code and then analyze the classes with gelint. The Contract Wizard generates wrapper classes as listed in Table 10 on the left hand side. I created a new Eiffel visitor class (CW_EIFFEL_TEST_VISITOR) based on the existing Eiffel visitor which generates Eiffel classes as listed in Table 10 in the right column. The wrapper features just have a "do end" as body and no dotnet_proxy feature. class CW_A feature foo is do dotnet_xxxxx.xxx end feature -- Implementation dotnet_proxy: DOTNET_A end class CW_A feature foo is do end end Table 10: Second set of classes These classes are Eiffel classe...
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to SYNTAX CHECK

  • Background Check The Department or Customer may require the Contractor to conduct background checks of its employees, agents, representatives, and subcontractors as directed by the Department or Customer. The cost of the background checks will be borne by the Contractor. The Department or Customer may require the Contractor to exclude the Contractor’s employees, agents, representatives, or subcontractors based on the background check results. In addition, the Contractor must ensure that all persons have a responsibility to self-report to the Contractor within three (3) calendar days any arrest for any disqualifying offense. The Contractor must notify the Contract Manager within twenty-four (24) hours of all details concerning any reported arrest. Upon the request of the Department or Customer, the Contractor will re-screen any of its employees, agents, representatives, and subcontractors during the term of the Contract.

  • Background Checks The State may require that the Contractor and Contractor Parties undergo criminal background checks as provided for in the State of Connecticut Department of Emergency Services and Public Protection Administration and Operations Manual or such other State document as governs procedures for background checks. The Contractor and Contractor Parties shall cooperate fully as necessary or reasonably requested with the State and its agents in connection with such background checks.

  • Contractor Personnel – Reference Checks The Contractor warrants that all persons employed to provide service under this Contract have satisfactory past work records indicating their ability to adequately perform the work under this Contract. Contractor’s employees assigned to this project must meet character standards as demonstrated by background investigation and reference checks, coordinated by the agency/department issuing this Contract.

  • Dues Checkoff Subd. 1.

  • Criminal Background Check The Academy shall comply with all sections 1230a of the Code and all applicable law concerning criminal background checks. In the event the Academy contracts with an ESP, the ESP shall comply with this section as if it were the Academy and certify such compliance to the Academy and the University President.

Time is Money Join Law Insider Premium to draft better contracts faster.