ChatGPT is also split...:
Given the circumstances, I would recommend extending define-method rather
than introducing define-method*.
Here’s why:
1.
*Consistency and Simplicity*: By extending define-method, you avoid
creating a dual system where users have to choose between define-metho
Thanks!
See responses to Tomas.
On Fri, Nov 22, 2024 at 1:20 PM wrote:
> Mikael Djurfeldt writes:
>
> Hello,
>
> > That was elegant. :-)
>
> :)
>
> > Nope---haven't seen it. (Or, at least I do not remember it.)
> >
> > Maybe I should have a look at what the optimizer can do about Mark's
> > cod
Hi Tomas,
Thank you for your feedback. Answers below.
On Fri, Nov 22, 2024 at 12:46 PM Tomas Volf <~@wolfsden.cz> wrote:
> I do find the symmetry between define-method/define-method* and
> define/define* pleasing.
>
Yes, I guess we are free to form GOOPS in our own style regardless of CLOS.
>
Mikael Djurfeldt writes:
Hello,
> That was elegant. :-)
:)
> Nope---haven't seen it. (Or, at least I do not remember it.)
>
> Maybe I should have a look at what the optimizer can do about Mark's
> code. (As you might have seen, my code is a modification of the method
> syntax implementation its
Hello,
opinion from the peanut gallery below.
Mikael Djurfeldt writes:
> Any opinions on what is best: Having a define-method* or having the
> functionality in define-method itself?
I do find the symmetry between define-method/define-method* and
define/define* pleasing.
For define and define*
