Re: Liberty-eiffel Digest, Vol 58, Issue 4

[Hans Zwakenberg]

I agree that ECMA compliance, or, considering our rather limited resources, at 
least strive in that direction would be a good thing…   :)



> liberty-eiffel-request@gnu.org hat am 06.07.2022 18:01 CEST geschrieben:
> 
>  
> Send Liberty-eiffel mailing list submissions to
>       liberty-eiffel@gnu.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.gnu.org/mailman/listinfo/liberty-eiffel
> or, via email, send a message with subject or body 'help' to
>       liberty-eiffel-request@gnu.org
> 
> You can reach the person managing the list at
>       liberty-eiffel-owner@gnu.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Liberty-eiffel digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: assign keyword (Raphael Mack)
>    2. Re: assign keyword (Louis M)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 05 Jul 2022 20:44:13 +0200
> From: Raphael Mack <ramack@raphael-mack.de>
> To: liberty-eiffel@gnu.org
> Subject: Re: assign keyword
> Message-ID:
>       <27ca6f068b03ee28cbd7bfa86d80d130fb910fe4.camel@raphael-mack.de>
> Content-Type: text/plain; charset="UTF-8"
> 
> 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
> release.
> 
> 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
> > end
> > 
> > class BAR
> > feature 
> >   foo: FOO
> >   do_something do
> >      foo.element := my_element
> >   end
> > end
> >     
> > In a few days I will add some tutorials about it.
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 5 Jul 2022 16:46:02 -0400
> From: Louis M <eiffel@tioui.com>
> To: liberty-eiffel@gnu.org
> Subject: Re: assign keyword
> Message-ID: <1000a330-0513-e541-a37a-fee0a7c61115@tioui.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> Hi,
> 
> 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
> > release.
> >
> > 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
> >> end
> >>
> >> class BAR
> >> feature
> >>    foo: FOO
> >>    do_something do
> >>       foo.element := my_element
> >>    end
> >> end
> >>      
> >> In a few days I will add some tutorials about it.
> >
> >
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Liberty-eiffel mailing list
> Liberty-eiffel@gnu.org
> https://lists.gnu.org/mailman/listinfo/liberty-eiffel
> 
> 
> ------------------------------
> 
> End of Liberty-eiffel Digest, Vol 58, Issue 4
> *********************************************