Changes between Version 69 and Version 70 of IR


Ignore:
Timestamp:
11/26/15 07:35:45 (10 years ago)
Author:
siegel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IR

    v69 v70  
    11
    22The CIVL-IR language.  A program in this language is also known as a "CIVL model".
     3
     4** CAN WE GET RID OF ALL \S EVERYWHERE???**
    35
    46Properties of the language:
     
    243245* `ATOMIC_EXIT;`
    244246* `PARSPAWN p, d, f;` where `p` is pointer to process reference, `d` has `Domain` type and `f` has `Function` type.
    245 * `NEXT dom, <i,j,…>;` : domain iterator: updates `i`,`j`,... to be the value of the inter tuple in `dom` after `<i,j,...>`
     247* `NEXT dom, <i,j,…>;` : domain iterator: updates `i`,`j`,... to be the value of the next tuple in `dom` after `<i,j,...>`
    246248* `FOR_ENTER dom;` **FIX ME**
    247249
     
    258260* `\pure` : the function has no side effects, but may be nondeterministic
    259261* `\abstract`: function is a pure, mathematical function: deterministic function of inputs
    260 * `\atomic_f`: function definition is atomic, and it never blocks
     262* `\atomic`: function definition is atomic, and it never blocks **ISN'T THIS TRUE OF EVERY SYSTEM FUNCTION?  IN WHICH CASE, IS THIS ONLY FOR NON-SYSTEM FUNCTIONS?**
    261263
    262264System functions:
     
    268270Example of a declaration of a system function with guard.
    269271{{{
    270 g(Real x, Bool y; Bool) { ... }
    271 f(Real x, Bool y; Integer) \guard {g};
     272g(x:Real):Bool { ... }
     273f(x:Real):Integer \guard g;
    272274}}}
    273275