Hi William,
> https://www.gnu.org/software/g-golf/manual/html_node/GOOPS-Notes-and-Conventions.html
> I found a paragraph which states "Except for virtual slots, there is
> currently no way to effectively prohibit (block) a user to mutate a
> goops class instance."
Actually, there is a way, b
Dear tran,
I think this question would be better suited for guile support channels
(like the GNU guile mailing list or #guile on libera IRC network) as
opposed to lilypond support, as your code examples don't include any
special lilypond procedures in them. I don't want to speak too much on
t
tran li writes:
> Recently I found that it is possible to use OOP in LilyPond Scheme by
> using the `oop goops` module so I would like to reconstruct some of my
> code in my `lily-score` project.
With all due respect: I would recommend more focus on using Scheme in
LilyPond Scheme first. You do
Recently I found that it is possible to use OOP in LilyPond Scheme by
using the `oop goops` module so I would like to reconstruct some of my
code in my `lily-score` project. However I encountered a problem with
the following example: I would like to design a class system for some
parametric cur
