27/05/2010: Implements Fiacre 2.0 plus the following experimental features:


shared variables:
-----------------

Shared variables may be read in any statement in a process (including
init statements and those performing communications).

Example (assiming v1 and v2 are shared variables):


	from S
	     if v2 > v1 then V1 := V2 else p!V1 end; to S'

As of  frac-1.4.0, shared  variables may be  written in  any statement
(including  those performing  communications) except  init statements.
frac checks absence of write  conflicts on shared variables at compile
time.


"on" statements:
----------------

The  "on"  statement, made  of  keyword  "on"  followed by  a  boolean
expression, is a derived  notation for guarded commands. A computation
path may include any number of "on" statements, at any place.

Semantically, the following statements are equivalent:
	      
     on e; s

     case e of true -> s end

     true := e; s


"loop" statements:
------------------

In a transition from state s,  the statement "to s" may be replaced by
"loop". In untimed transitions,  "loop" and "to s" behave identically.
In  timed  transition,  "to  s"  resets  the  clocks  of  all  enabled
interactions requiring state s, while "loop" does noit reset them.

Example:

	from S
	     if e then p!4; to S' else x := 3; loop end


"wait" statements:
------------------

Process  transitions may  include "wait"  statements, made  of keyword
"wait"  followed by  a time  interval (with  the same  syntax  as time
intervals in local port declarations of components).

Only  one wait  statement  may appear  on  any computation  path of  a
transition, and only in silent paths (not using any port).

Example:

	from S
	     if e then x := 0; wait [3,4[ else p!56 end;
	     to S'


"unless" clauses in select statements ("unless" statements for short):
----------------------------------------------------------------------

select statements are extended as follows:

select s_[]+ (unless s_[]+)* end

unless  clauses  specify priorities  between  alternants  of a  select
construction.  Only one select statement with unless clause may appear
on any computation  path of a transition. All  statements under unless
must be silent (may not use any port).

Example:

	from s
	     select s1
	     []	    s2
	     unless s3
	     []	    s4
	     unless s5
	     end

	In this example, statement s5 has priority over  s1 to s4 and
	statements s3 and s4 have priority over s1 and s2.


constraints on priorities:
--------------------------

In a priority specification  "a1 | ... | an > b1 |  ... | bm" ports ai
must be locally defined in the component or of profile closed.

frac also checks that the priority relation is cycle-free.


syntax revision:
----------------

Access   expressions  (a[x]   or  a.f)   are  now   considered  atomic
expressions.   As   a  consequence,  the   following  expresions,  for
instance, are grammatically correct:

   not a[3]          instead of        not (a[3])
   S (X r.f.[2])     instead of        S (X (r.f.[2]))

   etc,


any as sent value:
------------------

any is allowed as a value to be sent:

    p : ty1 # ty2 # ty3
    ...
    p!any,x,y

This form is a shorthand for:

   p : ty1 # ty2 # ty3
   ...
   a := any; p!a,x,y

But the type of a in that context is arbitrary (determined from the profile of p);

