Field replace statement should be an expression

Bug #408301 reported by Matt Giuca
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mars
Fix Released
Medium
Matt Giuca

Bug Description

The fieldreplace statement is weird. As it involves building a new object, then assigning it to a variable, it really has no place being a statement. The building of the new object should be an expression (fieldreplace) which may therefore be used in conjunction with an assignment statement to achieve the original goal.

Note that the i_fieldreplace instr doesn't have to change.

Tags: ir language

Related branches

Matt Giuca (mgiuca)
Changed in mars:
assignee: nobody → Matt Giuca (mgiuca)
importance: Undecided → Medium
status: New → Confirmed
Matt Giuca (mgiuca)
Changed in mars:
status: Confirmed → Triaged
Matt Giuca (mgiuca)
tags: added: ir
Matt Giuca (mgiuca)
Changed in mars:
milestone: none → 0.3
Matt Giuca (mgiuca)
tags: added: language
Matt Giuca (mgiuca)
summary: - fieldreplace stmt should be an expr
+ Field replace statement should be an expression
Revision history for this message
Matt Giuca (mgiuca) wrote :

Fixed in trunk r1098.

Changed in mars:
status: Triaged → Fix Committed
Matt Giuca (mgiuca)
Changed in mars:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.