[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: assign keyword

From: Louis M
Subject: Re: assign keyword
Date: Tue, 5 Jul 2022 16:46:02 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1


Personally, I think that we should go ECMA compliant. I know that historically, Small/Liberty Eiffel did not necessarily want to follow the ECMA standard, but I think that we will all win by not having too much difference between Eiffel syntaxes.

Good day,

Louis M

On 2022-07-05 14:44, Raphael Mack wrote:
Thanks Paolo for highlighting it. But let me raise the question for the
reason behind the inconsistency to the ECMA standard - which is clear
that the assign annotation shall be applied to the query to link it to
the appropriate set-procedure.

As we should go for releasing curtiss soon in my eyes, I would not want
to touch this, but right now I have the impression that it would be
better to deprecate the assign keyword on the setter even before we
released it and implement it in a ECMA-compliant way for dennis

Any opinions here on the list?

Am Dienstag, dem 05.07.2022 um 08:23 +0200 schrieb Paolo Redælli:
I added a note regarding the assign keyword to the release notes of
forthcoming Curtiss
  * added support for assign (note: it applies to the setter, while
ISE version applies to the getter)
For anyone not knowing this feature it allows to write things like
class FOO
feature set_element (a_element: like element) assign element

class BAR
   foo: FOO
   do_something do
      foo.element := my_element
In a few days I will add some tutorials about it.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]