1. 14 Oct, 2018 1 commit
  2. 21 Aug, 2018 1 commit
  3. 13 Dec, 2017 1 commit
  4. 29 Jun, 2017 1 commit
  5. 16 Jun, 2017 1 commit
    • Andrei Paskevich's avatar
      WhymL: break and continue · df239061
      Andrei Paskevich authored
      Without an argument, break and continue refer to the innermost loop.
      A label put over an expression sequence starting with a loop, can be
      used as an optional argument for break and continue:
      
        label L in
        [ghost] ["tag"] [M.begin]
          while true do
            ...
            break L
            ...
          done;
          [...]
        [end] [: unit]
      
      In the square brackets are listed the constructions allowed between
      the label declaration and the loop expression.
      df239061
  6. 06 Jun, 2017 1 commit
  7. 04 Jun, 2017 1 commit
  8. 03 Apr, 2017 1 commit
  9. 13 May, 2016 2 commits
  10. 10 Dec, 2015 1 commit
  11. 02 Jul, 2015 1 commit
  12. 13 Feb, 2015 1 commit
  13. 11 Sep, 2014 1 commit
  14. 14 Feb, 2014 1 commit
    • Andrei Paskevich's avatar
      WhyML: change the syntax of "abstract" · 4fd8b24d
      Andrei Paskevich authored
      The old syntax:   abstract expr [spec]...
      
      The semicolon binds more loosely than "abstract" and
      the specification clauses are optional, so that
      "abstract e1; e2" is the same as "(abstract e1); e2"
      and "abstract e1; e2; ensures {...}" is a syntax error.
      
      The new syntax:   abstract [spec]... expr end
      
      This allows to put sequences of expressions under "abstract"
      without ambiguity and moves the specification clauses to the
      beginning. In other words, "abstract" becomes a "begin" with
      a specification attached. The spec-at-the-top is consistent
      with the syntax of functions and the whole seems to be more
      natural for the intented use of "abstract" (a logical cut).
      4fd8b24d
  15. 20 Jan, 2014 1 commit
    • Andrei Paskevich's avatar
      WhyML: add "diverges", "reads {}", and "writes {}" effect clauses · 83858597
      Andrei Paskevich authored
      - "diverges" states that the computation may not terminate (which
        does not mean that is always diverges: just as any other effect
        annotation, this clause states a possibility of a side effect).
      
      - "reads {}" states that the computation does not access any variable
        except those that are listed elsewhere in the specification (or the
        proper function arguments, if "reads" is in a function spec).
      
      - "writes {}" states that the computation does not modify any mutable
        value.
      
      - If a function definition or an abstract computation may diverge,
        but there is no "diverges" clause in the specification, a warning
        is produced. If a function definition or an abstract computation
        always terminates, but there is a "diverges" clause in the spec,
        an error is produced.
      
      - If there is a "reads" or a "writes" clause in a function definition
        or an abstract computation, then every modified value must be listed
        in "writes" and every accessed external variable not mentioned in
        the spec must be listed in "reads". (Notice that this is a stricter
        requirement than before, when the presence of a "writes" clause
        did not require to specify "reads".) However, one does not have to
        write "reads {}" or "writes {}" if the corresponding lists are empty.
      83858597
  16. 03 Apr, 2013 1 commit
  17. 12 Oct, 2012 1 commit
  18. 22 May, 2012 1 commit
  19. 24 Feb, 2012 1 commit
  20. 12 Feb, 2012 1 commit
  21. 06 Feb, 2012 1 commit
  22. 08 Oct, 2011 1 commit
  23. 22 Aug, 2011 1 commit
  24. 01 Jul, 2011 1 commit
  25. 30 Jun, 2011 2 commits
  26. 31 Mar, 2011 1 commit
  27. 27 Aug, 2010 2 commits
  28. 08 Apr, 2010 2 commits
  29. 07 Apr, 2010 1 commit
  30. 06 Apr, 2010 1 commit