I have migrated some existing statements that are not liked by Guile-2 item 1. conditional define (if (condition) (define a ...) (define a ...)) (define a (if (condition) body1 body2)) item 2. curried define (define ((x a) b c) (display a) (display b) (display c)) (define (x a) (lambda (b c) (display a) (display b) (display c)))
and use cond-expand for backward compatibility Still don't know what's going wrong. I will try to extract the wrong pattern. Since it works in init-texmacs.scm but does not work in a module, I guess that the problem is related to Guile's Module System. ---- On Thu, 16 Jun 2016 06:46:51 +0800 Massimiliano Gubinelli <m.gubine...@gmail.com> wrote ---- Hi, On 15 Jun 2016, at 17:07, Darcy Shen <sad...@zoho.com> wrote: The problem is that after making tm-define.scm compile I can `tm-define` something in `init-texmacs.scm` and it compiles and works. But in the module `tm-preferences.scm`, it will cause a compile error where I use `tm-define`. do you know what is going wrong? If I remember correctly my attempts to Guile-2 there were statements which were mixing compile-time and run-time evaluations (like for example conditional definitions) and they were not liked by Guile-2. Max _______________________________________________ Texmacs-dev mailing list Texmacs-dev@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________ Texmacs-dev mailing list Texmacs-dev@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev
