[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Likely a good frog project for someone with C knowledge

From: Reinhold Kainhofer
Subject: Re: Likely a good frog project for someone with C knowledge
Date: Tue, 16 Aug 2011 23:36:15 +0200
User-agent: KMail/1.13.6 (Linux/2.6.38-10-generic; KDE/4.7.0; i686; ; )

Am Tuesday, 16. August 2011, 23:08:04 schrieb David Kastrup:
> Bertrand Bordage <address@hidden> writes:
> >     > Compile Lilypond with
> > 
> > I don't understand how you're applying this setting.
> > I tried
> > ./configure -DSCM.....
> > and
> > make -DSCM.....
> > without success.

You can even pass it directly to make:


See also the documentation in /usr/include/libguile/__scm.h (:
 * A value of 2 provides a maximum level of compile time type checking since
 * the SCM datatype will be declared as a struct.  This setting should be used
 * for _compile time_ type checking only, since the compiled result is likely
 * to be quite inefficient.  The right way to make use of this option is to do
 * a 'make clean; make CFLAGS=-DSCM_DEBUG_TYPING_STRICTNESS=2', fix your
 * errors, and then do 'make clean; make'.

However, I'm not sure if this will really work out or give us much benefit. 
In particular, we have lots of checks for == SCM_EOL or == SCM_BOOL_T. E.g. 
very deep inside the core of lilypond:

inline bool ly_cheap_is_list (SCM x) {return scm_is_pair (x) || x==SCM_EOL; }

Is this really not allowed?

We should definitely wait for Han-Wen to respond, since he is a Guile 
developer and probably has the deepest knowledge of us all. Before we get a 
definitive statement, I don't think it's a good idea to let any frog spend 
some time on it.

Reinhold Kainhofer, address@hidden,
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 *, DVR: 0005886
 * LilyPond, Music typesetting,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]