lp:~mgiuca/mars/fieldrep-expr
Making field replace an expression, rather than a statement (bug #408301).
- Get this branch:
- bzr branch lp:~mgiuca/mars/fieldrep-expr
Branch merges
Related bugs
Bug #408301: Field replace statement should be an expression | Medium | Fix Released |
Related blueprints
Branch information
Recent revisions
- 1104. By Matt Giuca
-
pretty: string_expr now has a precedence model, so it displays parentheses where necessary (presently, if a field-replace appears in the position of a 'primary').
- 1102. By Matt Giuca
-
parsem: Added extra production for 'primary'. Currently, expr just calls primary, but soon fieldreplace will be an expr, but not a primary (see doc/ref/exprs).
- 1101. By Matt Giuca
-
Added new expression type 'fieldreplace'.
Typechecks (currently just error), converts to CFG, and pretty-prints. No parser yet. - 1100. By Matt Giuca
-
doc/ref/expr: Fixed ambiguity in grammar relating to the new field_replace expression. Formally defined ':=' operator as right-associative and with the lowest precedence of all expressions.
- 1098. By Matt Giuca
-
Completely removed fieldreplace statement (supposed to be an expr, not a stmt). It was unused anyway (as the type checker rejected it), so this doesn't cause any distruption.
- 1096. By Matt Giuca
-
ir: Remove references to 'Venus' and comments that certain things are 'Mars only'. There is no Venus, only Mars.
- 1095. By Matt Giuca
-
Changed syntax for fieldset from 'e.f = v' to 'e.f =! v'. This gives it the scary syntax it deserves, being an impure update operation. (LP: #595782)
Branch metadata
- Branch format:
- Branch format 6
- Repository format:
- Bazaar pack repository format 1 with rich root (needs bzr 1.0)