[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: procedures with setters: patches
From: |
Han-Wen Nienhuys |
Subject: |
Re: procedures with setters: patches |
Date: |
Sat, 28 Feb 2004 13:25:23 +0100 |
address@hidden writes:
> Sat, 28 Feb 2004 11:53:15 +0100, Han-Wen a dit :
>
> > I'm ambivalent. The danger is that the number of functions to create
> > and manipulate data structures explodes, and becomes harder to
> > learn. We have to find a balance between having a small "interface"
> > and an interface that is ultra-ergonomic to use. For the above case, I
> > think make-music-by-name-and-props and is useful, althouh I oppose of
> > the name. Why not have
>
> > make-music-by-name
>
> > take an optional alist or list of init values?
>
> Of course, once there is a music maker that can have properties as
> arguments, former make-music-by-name has no use.
>
> By the way, why not `make-music'? I cannot find another
> make-music-by-something in the sources. It would look like
> (make-instance 'class-name ...options...) ==> instance of class-name.
It was a transitional name, I guess ; I forgot.
> (make-music 'OverrideProperty
> 'symbol 'Stem
> 'grob-property 'thickness
> 'grob-value (* 2 1.5)
> 'pop-first #t))
> ==>
> <OverrideProperty :pop-first #t
> :grob-value 3.0
> :grob-property thickness
> :symbol Stem>
>
> If that's OK, I may build some patches.
go for it.
--
Han-Wen Nienhuys | address@hidden | http://www.xs4all.nl/~hanwen