Le 19/10/2022 à 22:47, Jean Abou Samra a écrit :
This code is behaving as expected. The manual's description of the
example
and the naming "*compilation-date*" look buggy, however.
I've submitted a patch to fix this.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58646
Best,
Jean
Le jeudi 20 octobre 2022 à 10:53 +0200, Maxime Devos a écrit :
> If so, this is not exactly what I am looking for. I am looking for a
> > way to run the (date) form during the compilation phase, and save
> > the
> > date to the compilation unit so that it does not change. Is this
> > possible?
>
On 19-10-2022 22:32, Vivien Kraus wrote:
Dear guile users,
The manual, section 6.8.8, presents the eval-when form with an example:
> [...]
If so, this is not exactly what I am looking for. I am looking for a
way to run the (date) form during the compilation phase, and save the
date to the
Le 19/10/2022 à 22:32, Vivien Kraus a écrit :
Dear guile users,
The manual, section 6.8.8, presents the eval-when form with an example:
(use-modules (srfi srfi-19))
(eval-when (expand load eval)
(define (date) (date->string (current-date
(define-syntax %date (identifier-syntax (date)))
Dear guile users,
The manual, section 6.8.8, presents the eval-when form with an example:
(use-modules (srfi srfi-19))
(eval-when (expand load eval)
(define (date) (date->string (current-date
(define-syntax %date (identifier-syntax (date)))
(define *compilation-date* %date)
I take the
