fomus-devel July 2005

fomus-devel@common-lisp.net

4 participants
13 discussions

[fomus-devel] settings
by Rick Taube 20 Jul '05

20 Jul '05

It would be helpful it you would list and/or describe the default value that fomus initially assigns to each parameter: :AUTO-ACCS-FUN [nil] or whatever. also what does the -FUN suffix mean?? function? but the value I pass is a keyword, not a function. if you mean that internally fomus uses a function then i dont think the user cares if you do it with a function or a hamster, its not really relevant to me if i cant pass a function. I would be happy to trade that information for a shorter name: :auto-accs :nokey1 what does the 1 mean after the names like nokey1? i dont see a 2 anywhere so why do i have to always add a 1?? even if there is a 2, i will never remember what 1 vs 2 means so i will always have to refer to the docs. using keywords as parameters is nice, and since there are so many of then and since you define them as globals inside fomus you could associate documentation each parameter so users could look up what they need in the repl: (fomus:doc :auto-accs) "controls the foo of bar. possible values are: bif buf. current valuee is buf. defaut value is zuz. (fomus:doc :part) the following settiing are defined for class PART: asd,qw3e, asd, xcv

1 0

[fomus-devel] compiling in sbcl
by Rick Taube 20 Jul '05

20 Jul '05

fomus will not compile in sbcl 0.9.0 on OSX: ; compiling (DEFPARAMETER +LILYPOND-DYNS+ ...) ; compiling (DEFUN SAVE-LILYPOND ...)set_auto_gc_trigger: tried to set gc trigger too high! (0x081a3e98) fatal error encountered in SBCL pid 1317: lost The system is too badly corrupted or confused to continue at the Lisp level. If the system had been compiled with the SB-LDB feature, we'd drop into the LDB low-level debugger now. But there's no LDB in this build, so we can't really do anything but just exit, sorry. it does compile and load in cmu and openmcl.

1 0

[fomus-devel] loading fomus
by Rick Taube 20 Jul '05

20 Jul '05

Hi the docs say: > Example 2.1. Compiling and Loading > CL-USER> (load "path_to_fomus_directory/load.lisp") but this does not work in either openmcl or cmucl or sbcl. there are several problems, the first is that neither openmcl or cmucl have the ASDF package preloaded, so when you do your READ: (with-open-file (f (merge-pathnames "fomus.asd" *load-pathname*) :direction :input) (destructuring-bind (xxx1 xxx2 &key components &allow-other-keys) (read f) it breaks because your fomus.asd assumes there is an asdf package: (asdf:defsystem "fomus" i dont think i makes any sense to read that file: either insure that asdf is aroun, load the file and call asdf:operate or dont assume the asdf package at all. the second problem is that (file-write-date cn) will return NIL if cn does not exist: ? (file-write-date #P"/Lisp/fomus/package.dfsl") NIL which breaks your >= date comparison. this fixes both issues and works in openmcl cmucl and sbcl ------------------------------------------ fomus/load.lisp ;; -*-lisp-*- ;; Load file for FOMUS (defparameter *components* '("package" "misc" "deps" "data" "classes" "util" "accidentals" "beams" "marks" "other" "ottavas" "parts" "postproc" "split" "staves" "voices" "quantize" "backend_ly" "backends" "main" "interface" "final")) (loop for na in *components* for cl = (merge-pathnames na *load-pathname*) for cn = (compile-file-pathname cl) for wd = (file-write-date cn) when (or (not wd) (>= (file-write-date cl) wd)) do (compile-file cl) do (load cn))

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

fomus-devel July 2005