Grep for TODO and ugh/ugr/urg.
.* BUGS
-. * header for PS enteredby = "bla <bla@bar.com>"
-. * Hash_table::remove ().
-. * 1. With "lilypond -f ps": The black notes with ledger lines seem to
-> have extra "blobs" over and to the left of them and all the ledger
-> lines from the staff to the note will have a blob too. For example,
-> with the note "a4" there will be a black note at the ledger line where
-> "c" would be too. However, only the "a4" will have the extra blob.
-. * clefs.ly
-. * ps/lily.ps
-. * devise standard for functioning of Vertical_align_element.
-. * fix interstaff slurs & beams.
-. * staff size for post/prebreaks
-. * .ly files
-. * input/star-spangled-banner
-. * input/scripts.ly
-. * mutopia/J.S.Bach/wtk1-fugue2.ly
-. * input/test/grace
-. * fix: text on rests: ridiculous dims
-. * clefs.ly
-. * m=\notes\relative c'''{
- \time 2/4;
-
- R2*4 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | \break
- <{R2*10}{s2 \mark "A"; }> | % Too narrow space for the first rest in
-1.1.29
- r4 r8 [g16 \p ( a ] |
-[ ) g8-. fis16 ( g ][ ) fis8-. f16 ( g ] |
-[ ) f8-. e16 ( f ][ ) e8-. es16 ( f ] |
-[ ) es8 \f c16 ( d][es8 d16 c ] |
-) d4 r8 [g16 \p ( a ] |
-[ ) g8-. fis16 ( g ][ ) fis8-. f16 ( g ] | \break
-) c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 | c2 |
-}
-
-\score{
- \m
- \paper{
- \translator{
- \ScoreContext
- SkipBars = 1;
- }
- \translator {
- \OrchestralPartStaffContext
- }
- }
-}
-. * midi key.
-. * P.P.S. It can be cool in mudela-book to distinguish in pre,postMudelaExample,
-whether MudelaExample is epsed or not: ( if this fragment is floating eps, than 1,
-otherwise 2). say preMudelaExample[eps]{}, and change it in document body sometimes.
-. * fix singleStaffBracket
-. * declare performers in \midi
-. * fix MIDI
+. * sane strategy for extensions (assume .ly):
+02:22:24 appel ~/usr/src/lilypond$ lilypond foo
+GNU LilyPond 1.1.54.
+[/home/fred/usr/src/lilypond/scm/lily.scm]
+warning: can't find file: `init'
+. * indent = 0.0 with linewidth=-1.0
+. * music ending in grace notes.
+. * PostScript
+. * half notes in pfa
+. * didot / big point.
+. * check EGCS version
+. * input/test/stem-spacing.ly: 12/4 touches first note
. * \shape 1st dim skipped?
. * turn slope-damping on/off
-. * tremolo stuff
-. * fix height of / collisions with lyrics (chords),
- see input/test/vertical-text.ly; input/test/repeat.ly
. * We need feta-din*.mf files for more sizes than 10.
-. * latex bla.tex broken (titles / \lilyfooter stuff?
. * fix dynamics decently, ie. use kerning & ligatures.
. * dots & rest collisions?
-. * mudela-book.py
-. * \mudelafile{} to have decent functionality
-. * use less RE's
-. * support_l_arr_ empty in staff-margin's G_staff_side_item
-. * slurs colllide with lyrics.
-. * minVerticalAlign for StaffGroups.
-. * fix OrchestralScore and Hara-kiri (i.e., fix Coriolan)
-. * Phrasing: Indicating the textual underlay of a piece, or
-otherwise dividing a piece into phrases.
-
-There are distinct ways of specifying the first two (although at
-present, they're not properly distinguished) but no distinct way to
-specify the third. Should there be?
-. * spacing of mmrests.
-. * mem leak: redo p-score object deletion.
-. * rest collision minimum dist.
-. * Matanya's tips:
-. * spacing for prefatory matter
-. * Score does not use points to describe musical sizes. I think becaue the music
-> symbols are not part of any PostScript font. The line length is 7.5 inch (19.05
-> cm) and the height of normal size is equivalent to the traditional raster 1
-> size. (The Schott company sells Letraset sheets of musical symbols which are
-> measured in raster sizes). It is agreed among most engravers I know that the
-> standard size for adult readers in solo music should 70% of raster 1. Jeff's
-> example was 75%, so I had to modify my file to match. Of course, the amount of
-
-So that makes for a staff space of 4 2/3 point. I'll add the
-dimensions to the TODO file.
+. * behavior of "that the obvious solution
+\lyrics { foo1*4 __ _ }" is unintuitive.
+. * Lyrics and scripts collide.
+. * a note with a circle after it, meaning:
+
+ note + circle = note + 1/4 of its length
+
+ the circle is like a dot that's not filled in. for example, on
+ page three, the c-sharp on the second line should be a quarter with
+ a circle, not a quarter tied to a sixteenth. is this at all
+ possible with lily?
+. * grace_align_item -> stackingdir = left, weird placement.
+. * grace before triplet, see standchen
+. * tuplets that are written as "number : note", for example
+ "3 : [image of a half note here]". possible?
+
+. * filenames : junk lily.x
+. * Matanya's tips:
+. * don't shorten stems/staffs closer to each other.
. * accidentals closer to note head
-. * ledger line for rest dim less
+. * to space the staffs/staffgroups contained in the score.
. * heavier beams?
-
.* Cleanups needed
+. * \$ and $ identifier syntax in examples.
+. * bracket ps code.
+. * Key_engraver, Local_key_item
+. * Think of comprehensive solution for "if (grace_b == self_grace_b_)"
+. * Y dimension units: staffspace vs. Point
. * Beam
-. * Stem + Notehead
+. * Stem
+. * Rhythmic_column and interaction stem/rhythmic_column/note_head/dots.
. * Slur
-. * Repeats
-. * Rhythmic_grouping
. * Duration
-. * Spring generation
-. * Collision
-. * Rest_collision
+. * clef engraver
+. * parser
.* TODO before 1.2
-. * \selectmusic to cut pieces from music.
+. * rename midi2ly, abc2ly mup2ly
+. * Grace_slur_engraver.
+. * Break_req handling is silly (break_forbid () + \break fucks up.)
. * Morally pure LilyPond.
-. * Remove mutopia ramblings.
. * Remove non-free software links.
. * Remove meta article LilyPond.
-. * TODO: merge atom & molecule; make tree from molecule.
. * break priority setting from SCM.
-. * Gade score
-. * remove [] in favour of auto-beamer
-. * The minimum distance between different staffs works only within
- StaffGroups, not between StaffGroups. The Gade Score looks quite
- strange on the pages where the Timpani and/or Brass sections don't
- play. I've set the minimum distance with:
- \translator {
- \OrchestralScoreContext
- minVerticalAlign = 2.5*\staffheight;
- }
. * hangOnClef with non-breakable clefs.
-. * Aha, the problem is the new TeX code generation for changing fonts.
-> (The explanation below is mostly intended for Han-Wen and Jan)
-> Before, the font was changed with macros declared separately for
-> pure TeX and LaTeX, but now all the fonts are declared directly in
-> the generated code using the low-level TeX commands. This circumvents
-> the fontencoding mechanism of LaTeX and is a potential source of
-> problems also for us users of the Latin-1 character set.
-> I think it still works since the inputencoding latin1 is
-> declared by ly2dvi, but it still means that e.g. an o with
-> umlaut is typeset as a combination of the two symbols 'o' and
-> 'umlaut' instead of as a single character, as would be the case
-> if fontencoding OT1 had been used. This shouldn't give any
-> difference in layout, though. One of the main argument for using
-> fontencoding OT1 is for the hyphenation mechanism to work, an
-> argument that's clearly irrelevant in our application. Yet we
-> see the problem for August.
-. * Check gcc 2.8.1 compatibility
. * Abstraction for engravers:
. * make "in-between" engraver (Tie, Extender)
-. * make wide_spanner_engraver (line_group_spanne,r staff_symbol)
-. * remove Interval dim_ from Dimension_cache and rename the struct.
+. * make wide_spanner_engraver (line_group_spanner, staff_symbol)
. * do scaled fonts generally
-. * The Lilypond accidental symbols are available through the TeX macros,
-\textflat, \textsharp and \textnatural defined in the init file
-lilyponddefs.tex. All the symbols are defined in the files fetaXX.tex
-where XX corresponds to the size. I don't know where (or even if) they
-are installed but they are generated in the mf/out/ directory during the
-compilation.
. * make dependencies () a virtual function.
-. * fix Repeated_music design
-. * one big ly2dvi input that includes *all* tests.
. * store req -> element, element -> element causes for warnings
. * include examples in RPM.
. * fix partial measures in meaningful way.
-. * add scripts to bars eg. |^"bla"
. * relative mode for mi2mu
. * uniformise recent feta contributions.
-. * use SCM and Molecules for {accordeon stuff, }
. * bigger and fatter 4/4 C
. * sort out directory stuff.
. * --prefix option?
. * do --safe for PS output?
. * convert-mudela --output
. * Staff_margin (with a partial measure.)
-. * fix pletvisibility properties:
-. * bracket on/off/no-bracket-when-beam
-. * num on/off/no-num-when-beam
-. * fix: standchen.
-. * junk text{sharp,flat,etc}
. * fix convert-mudela manpage
. * decimal point in \paper {}
-. * { \voiceone <a'4.*2/3 d''4.*2/3 fis''4.*2/3> [g''8 fis'' e''] d''4 |}
- and
- { \voicetwo d'4 d'2.*2/3 } spacing
-. * tied notes for MIDI
-. * sharp / flat on trills (in MIDI ??)
. * scm-ify \property values.
. * move class Lookup {} into scm
. * msgfmt -o check?
-. * \breathmark TeX macro
. * add new glyphs to font.ly
. * formatting of input stuff.
-. * \notes{ a \< b \cr } vs \notes{ a \< b \! }
-. * space after bars?
-. * 'hinterfleisch' before bar (e.g. wtk1-fugue2)?
-. * Summary of minor spelling irregularities:
-. * capitalization/use of underscores in property names
-. * fix SkipBars -> skipBars
. * broken scripts:
lbheel = \script { "bheel" 0 0 -1 0 0 }
rbheel = \script { "bheel" 0 0 1 0 0 }
rfheel = \script { "fheel" 0 0 1 0 0 }
lftoe = \script { "ftoe" 0 0 -1 0 0 }
rftoe = \script { "ftoe" 0 0 1 0 0 }
- and also
- portato= \script { "portato" 0 -1 0 1 0 }
-. * ly2dvi
-. * bottomnote for ly2dvi
. * deps for ly2dvi
+
+. * decide wether to junk _ in lyrics.
+
.* STUFF
. * compulsory hshift
+. *
+My wish list for lyrics. I dream of a time when I will have enough time to
+become familiar enough with the source code to be able to implement some of
+these myself, but I don't know when that will be, so I thought I'd "publish"
+my suggestions in case someone else is in a position to give them some
+priority. Otherwise, perhaps they could go on the todo list?
+
+If any of these are already implemented, please let me what the syntax is to
+use them!
+
+1. Stanza numbering. Numbering at the beginning of a song with the number
+set to the left of the first note. It would also be nice (but not as
+important) to be able to have some form of automatic numbering at the
+beginning of each new line. This would make it easier to follow songs with a
+large number of stanzas.
+
+2. Hyphens between syllables. At the moment there appears to be no easy way
+to position a hyphen mid-way between the syllables it breaks.
+
+3. Notes centred above/below lyrics rather than left-aligned.
+
+4. It would be very nice to be able to build some kind of phrasing into the
+lyrics of hymns, etc, so that the first words of a phrase are left aligned
+with each other, the last words are right aligned, and the words in between
+are centred.
+
+5. In a song, with (say) four stanzas and a chorus, it would be nice to be
+able to vertically align the chorus midway between the staves.
+
+6. It would be nice to be able to put vertical brackets either side of a
+repeated section with different words for each repeat.
+
. * Give # lines in linebreaking.
. * arrows on slurs.
+. * rewrite context defs using Scheme
+. * \selectmusic to cut pieces from music.
+. * TODO: merge atom & molecule; make tree from molecule.
. * Align_element::padding ?
-. * uniformise property names...
-. * ydirection <-> yDirection
-. * rather allow '_' in identifiers first (i.e. junk ^ and _),
-and do y_direction?
-. * typo checks on property names?
+. * typo checks on property names?
. * use streambufs and iostream
to provide IO handling for TeX stream, mudela stream, data-file.
. * seriously buffer TeX output (do profile of writing .5 mb TeX file.)
. * zip target for binary windows dist (JBR)
. * junking \skip req in lyrics
. * mi2mu empty staffs.
+. * use Fourier transformation for rhythmic quantisation.
. * horizontal centering of dynamics
. * $DEPENDENCIES_OUTPUT support
-. * Xdvi zooming ?! Try to understand GS garbage collection.
-gs: Error: /undefined in draw_beam
-gs: Operand stack:
. * fix vertical alignment and stafflines
. * declaring Performers
-. * GrandStaff needs more work -- I want a single word
- `harpsichord' to the left of the grandstaff, not one on each
- stave. (Organ staff -- with separate pedal -- but common
- properties may be something to think about. Of course for
- organ you want to be able to give stop indications on the way
- through, so the \property Voice.Instrument would be a stop,
- and \property GrandStaff.instrument would be PipeOrgan...)
. * *.yo: fix pod manpage layout legacy
. * text-items clash with stems/beams
. * --include, -I option for ly2dvi (pass on to lily)
* { a4 a16 } c <-- duration of c?
* < a4 b8 > c <-- duration of c?
. * \tempo 4. = 90;
-. * fix audio-items (don't use (input) requests, but copy data)
. * make sure all ex's have a mudela-version
. * do rest-collisions for Multi_measure_rests as well.
. * split error/warning in error/warning/non_fatal_error
. * fix title/instrument placements; see input/test/title.ly
. * <\voiceone c4. \voicetwo c4>
. * add full cello suites to web site (kom op, Maarten!)
+. * add mudela-book-doc source to webstie.
. * Rethink Time_description
-\cadenza , \meter, \grouping should all be \properties
+\cadenza , \meter, should all be \properties
+. * fix singleStaffBracket
. * rename
. * measure -> bar
-. * abbrev -> tremolo
. * abbreviation-beam -> (measured/unmeasured) tremolo
. * partial -> anacrouse
. * robustify Beam (in case of no stems, 32nd notes)
touching it.
. * put errorlevel in Input class
. * junk nesting slurs
-. * integrate midi-elts from mi2mu and lily?
+. * distinguish between unset and empty properties.
.* FONT
. * the bracket is ugly (wings are too parabolic, should be more circular)
. * versioning for Feta
+. * rewrite dynamic signs. They're kind of spaghetti now.
. * The `3' in the meter key is a one or two pixels too thin (at 600dpi)
in the middle:
. * design macro for penstroke with rounded endings
. * timesig C: fat yet less curved. Check out relations.
. * design decent macro for bulbed endings
. * printer dependencies.
-. * y-refpoint for rests should be the 4th staffline (gclef: b')
-. * clean-up eight+ rests
. * versioning
. * lo-res fixes.
. * work out sizes of character fonts.
. * coda signs: Segno, O+
. * glissando, arpeggio
. * lengthened trill
-. * 128th flags
. * include important spacing dims in fetalog
+. * scalability: use blot_diameter everywhere, make font chubbier for
+ small sizes.
+
.* 3RD PARTY BUGS
+. * UMR: Uninitialized memory read
+ This is occurring while in:
+ qst [qsort.c]
+ qsort [libc.so.1]
+ Keyword_table::Keyword_table(Keyword_ent*) [keyword.cc:28]
+ My_lily_lexer::My_lily_lexer() [my-lily-lexer.cc:78]
+ My_lily_parser::parse_file(String,String) [my-lily-parser.cc:54]
+ do_one_file(String,String) [scores.cc:124]
+ Reading 4 bytes from 0xefffeca8 on the stack.
+ Address 0xefffeca8 is 728 bytes below frame pointer in function
. * GNU diff 2.7: diff -rN does not see a new directory with empty file
+. * patch: don't touch timestamp if all patches fail.
+. * mf-to-table -> add space before ; in AFM output. (-> check AFM
+ spec. Is this a bug in afm2tfm?)
. * check out GCC signatures?
. * glibc 2.0:
f = fopen ("/dev/null", "r")
assert (feof (f))
. * tetex: mfplain.mem
+. * timesig: sometimes bottom digit too high: Xdvi doesn't handle
+ newly created fonts correctly.
.* 3RD PARTY PROJECTS:
. * make GCC warn about ctor that leaves member vars uninitialised.
. * GNU patch
thing is fixed
.* PROJECTS
. * Scripts:
-. * fix position of bar number
. * stack scripts in chords:
% fingering: footing:
< a-4 c-2 g-1 > < c-\ltoe e-\lheel >
. * PS output
. * optimal pagebreaking.
-. * Unicode support? -> man 7 unicode
-. * 16 bit Strings
-. * -u switch
-. * detect of 16/8 bit files
-. * examples to go with it.
-
-. * Spring_spacer:
-. * write a faster Spring_spacer (without matrices if possible)
-. * relate energybound to linelen unitspace fontsize etc.
-. * used fixed point fp?
+. * internationalisation for input.
+. * Unicode support? -> man 7 unicode
+. * (The explanation below is mostly intended for Han-Wen and Jan)
+> Before, the font was changed with macros declared separately for
+> pure TeX and LaTeX, but now all the fonts are declared directly in
+> the generated code using the low-level TeX commands. This circumvents
+> the fontencoding mechanism of LaTeX and is a potential source of
+> problems also for us users of the Latin-1 character set.
+> I think it still works since the inputencoding latin1 is
+> declared by ly2dvi, but it still means that e.g. an o with
+> umlaut is typeset as a combination of the two symbols 'o' and
+> 'umlaut' instead of as a single character, as would be the case
+> if fontencoding OT1 had been used. This shouldn't give any
+> difference in layout, though. One of the main argument for using
+> fontencoding OT1 is for the hyphenation mechanism to work, an
+> argument that's clearly irrelevant in our application. Yet we
+> see the problem for August.
. * \header
. * output header info to MIDI too.
. * a musical dictionary. See Documentation/vocabulary-*, other
- languages:
+languages:
. * explanations
. * italian
. * german
. * SMDL?
. * add to MIDI output:
+. * sharp / flat on trills (in MIDI ??)
. * tempo change
. * ornaments (and trills?)
-. * repeat/volta
. * slurs
. * accents
. * dynamics
> Would it be hard to add support for proper dynamics in MIDI output? I
> would really like to have this feature...
-To answer this, I have to give a little background. Please say so if
-I am being obtuse.
-
-Both audio and notation elements are created decentrally, when
-LilyPond says "Interpreting music ... [8][16] etc." After all
-elements are created, they are processed again to calculate all
-parameters. After that is done, they are dumped onto the output (the
-MIDI stream or the TeX file).
-
-The audio and notation elements are created by objects called
-performer and engraver respectively. They work by taking a chunk of
-input (a so-called request), and using the request to create an audio
-or notation element.
-
-After some processing, the engraver sends the created elements to
-its enclosing notation/performance context.
-
-In the case of notation, engravers can also modify existing elements
-created by sibling engravers. Eg. the beam-engraver will modify stems
-when it creates a beam over a couple of stems. This is done in
-Engraver::do_acknowledge_element () and
-Engraver::do_process_acknowledged ().
-
-In the case of audio, there are no mechanisms to modify existing audio
-elements. After the audio elements are created, they are sent directly
-to the enclosing context (an instance of Performer_group_performer),
-through the method Performer::play ()
-
Concretely spoken, for dynamics you have to write a performer
(Dynamics_performer), that will take the input requests. If I
understand correctly, every MIDI note played must have its dynamic
1 supporting dynamic settings in Audio_note
- 2 mimicking the broadcast/acknowledge mechanism of the Engravers in
- the Performers
-
- 3 using that mechanism to write a Dynamics_performer that will modify
+ 2 Write a Dynamics_performer that will modify
any notes it finds to set appropriate strengths.
-You could also kludge this by deriving from Performer_group_performer
-a performer that also sets dynamics within notes, but that is not the
-elegant way to do it.
-
I'd say that the work involved is not hard, but you have to be fluent
with C++ and need some insight into the working of Notation Contexts
and friends. I guess I could do it in a day or so, but if you are not
the MIDI output (I don't even have a soundcard). But I *do* want to help
you or other people with implementing this, so if you need help, don't
hesitate to ask.
-
. * account for rhythmic position in measure
. * etc.
-. * grace notes
-. * make separate class for Grace_*_engravers
- (which is at Voice_gravs level)
-. * make encapsulated spacing problems.
-
-. * accidentals per Voice_group
. * Output class, handles : (smallish)
. * help text /(c) notice?
. * Glissando
. * trill
-. * Rewrite Stem, Beam and Rhythmic_grouping (hairy)
-. * [c8. c32 c32]
-. * doc on Rhythmic_grouping
+. * Rewrite Stem, Beam (hairy)
. * general shaving on Beam and Stem
. * use plet grouping
-. * separate visual from rhythmic info even more
. * beams over bars
. * lines:
. * specify number of lines
.* INPUTLANGUAGE
-. * \rhythms 4 16 16 16 16; c c c c c -> c4 c16 etc.
+. * convention for slurs vs. phrasing marks.
. * Language:
-. * \type -> \context ?
. * \translator -> ?
. * fix \partial
. * \bla {} vs \bla ;
. * mix engraver hacking with music ?
. * \once\property KEY = VAL
-. * \addtranslator, \removetranslator
-. * junk ^ and _ for scripts
-. * junk _ for lyrics.
+. * input property
. * abstract grammar.
. * Figure out semicolons.
. * c4 4 4 4 for c4 c4 c4 c4?
.* SMALLISH PROJECTS
-. * Faulenzer sign (% repeat)
-
. * fix confusing naming in Engraver vs Engraver_group_engraver (context)
-. * progress when creating MIDI elts.
-
. * A range for context errors (eg. mark both { and }. )
. * lyric in staff (sharpsharp in staff, text below)
-. * half sharps/flats
-
. * write Dynamic_line (to group dynamics horizontally)
. * use Real for all y positions.
. * midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
-. * stafftypes: voice names/ instrument names.
-
. * lily \tempo
. * % toe to bheel four to five
(where "to" is a tiny bow)
. * auxilliary file for caching info.
-
. * Text_crescendo
-. * revise calcideal
-
.* IDEAS
. * Output data structures of Mudela in XML/SGML.
. * create libmudela, or liblily_frontend
. * Spacing_request for manually adjusting spacing
. * caching breakpoints
. * used fixedpoint arithmetic for min. energy.
-. * move towards incremental algorithms.
-. * versioning stuff (cvt mudela, mudela, etc.)
-. * dynamic loading of engravers?
-.* SMOBS
-Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
-
-> class Foo_class {
-> Foo_smob *smob_ptr_;
-> }
->
-> struct Foo_smob {
-> Foo_class *class_ptr_
-> }
-
-Usually you can get away without having this interlinked structure.
-One piece of information you need when exporting objects to scheme is
-the smob tag for your class. You might store this value (a long) into
-a class static variable, or a file static variable. I'll use a class
-static variable in this example.
-
-I typically use code that works like this (untested code ahead):
-
-class Foo_class {
- static long *Foo_smob_tag;
- SCM obj; // representation as a scheme object, description comes later
-}
-
-// call this once on startup
-void init_Foo_class {
- static scm_smobfuns type_rec;
-
- type_rec.mark = foo_mark;
- type_rec.free = foo_free;
- type_rec.print = foo_display;
- type_rec.equalp = 0;
- Foo_class::Foo_smob_tag = new int(scm_new_smob(type_rec));
-}
-
-When you want to export an object to scheme, you put a pointer to the
-object itself in the cdr of the cell, and the tag in the car of the
-cell. The code looks like this:
-
-// Is this a Foo?
-static int
-foo_p(SCM obj)
-{
- return(SCM_NIMP(obj) && SCM_CAR(obj) == Foo_class::Foo_smob_tag);
-}
-
-// given a Scheme representation, return, a C++ representation
-static Foo_class *
-foo_unbox(SCM obj)
-{
- return((Foo_class*)SCM_CDR(obj));
-}
-
-// the SCM representation of the object is stored inside itself
-// this will become useful when destructor gets called
-static SCM
-foo_box(Foo_class *foo)
-{
- SCM_DEFER_INTS;
- SCM_NEWCELL(foo->obj);
- SCM_SETCAR(foo->obj, Foo_class::Foo_smob_tag);
- SCM_SETCDR(foo->obj, (SCM)foo);
- SCM_ALLOW_INTS;
- return foo->obj;
-}
-
-> C++ determines life time, so what is the strategy?
-
-What happens now when the destructor gets called? Lets set the cdr to
-NULL, and then check for that in all of the primitive functions that
-use your smob. We'll call this notion 'live'; a scheme object is
-'live' if the C++ representation still exists, it's dead if the C++
-object is gone. You can still have references to dead objects in
-scheme code; it's just an error to use them. This idea is stolen from
-Emacs's handling of buffers ('buffer-live-p' and friends).
-
-Add another function, foo_live_p:
-
-static int
-foo_live_p(SCM obj)
-{
- return(foo_p(obj) && SCM_CDR(obj) != NULL);
-}
-
-In you destructor, you need to do:
-
-~Foo_class()
-{
- SCM_CDR(this->obj, NULL);
-}
-
-When writing new primitives, now just check foo_live_p().
-
-I hope the above helps,
-
--russ
-
-
---
-"Even if you are on the right track, you'll get run over
-if you just sit there."
- --Will Rogers (1879-1935)
* OUTLINE SETUP
.* .EMACS
projects / lilypond.git / blobdiff