Trac2GitHub Transition of Modelica Assocication Projects

**Comment by anonymous on 13 Jun 2014 15:12 UTC** Replying to [comment:3 otter]: > Since the grammar identifies a function call by "name(", one would have to find something else,...

**Comment by hansolsson on 15 Jun 2014 17:57 UTC** Some comments: * The replaceable restriction does not make sense to me. I see no difference between redeclaring the component (in...

**Comment by hansolsson on 15 Jun 2014 18:05 UTC** Forgot to add that the subtyping argument also means that we really need to use named arguments (which is already part...

**Comment by sjoelund.se on 15 Jun 2014 18:57 UTC** Wouldn't a much nicer syntax for multiple outputs be: ```mo Real r; Boolean y; equation (r,y) = OnDelay(u=..., delayTime=...); ``` Anyway,...

**Comment by hansolsson on 15 Jun 2014 19:10 UTC** Replying to [comment:7 sjoelund.se]: > Wouldn't a much nicer syntax for multiple outputs be: > ```mo > Real r; > Boolean...

**Comment by otter on 25 Jul 2014 13:35 UTC** Updated the proposal according to the Dymola prototype of Hans: ``` // Instead of Real r = OnDelay(...) // Dymola prototype...

**Comment by petfr on 20 Nov 2014 09:47 UTC** The problem with accessing outputs via OnDelay.y is that you can not anyway write block calls to blocks with more than...

**Comment by petfr on 20 Nov 2014 09:54 UTC** The restriction to only allow calls in the bindings of variables seems arbitrary and unnecessary. From an implementation point of view,...

**Comment by petfr on 20 Nov 2014 10:00 UTC** Proposed restriction says: > The expression in which the block is called is not conditional. Why is this restriction necessary, and...

**Comment by petfr on 20 Nov 2014 10:08 UTC** An alternative syntax for accessing more than one output could be: ```mo Real x,y; equation (x,y) = MyBlock(...).{y1,y2} ``` This could...