From: Damien Mattei <damien.mattei@gmail.com>
Cc: Kawa mailing list <kawa@sourceware.org>
Subject: Re: variable definition in include files not usable in class file
Date: Tue, 03 Oct 2017 15:35:00 -0000 [thread overview]
Message-ID: <CADEOadeTNueSDEM-35E=Opbgzxtf_uO71SEtg6DvbeEbZD9zJA@mail.gmail.com> (raw)
In-Reply-To: <CADEOaddDyMoG9w9UBUiBnMunmtBeH5pJh0=bRbFFKfrXTvnYZA@mail.gmail.com>
i wanted to say 'can not explain' in my previous message
Regards,
damien
On Tue, Oct 3, 2017 at 5:33 PM, Damien Mattei <damien.mattei@gmail.com>
wrote:
> possible, but i can explain it works in Bigloo if this one does not
> respect hygienic expansion, but Bigloo do it:
> https://www-sop.inria.fr/indes/fp/Bigloo/doc/bigloo-25.
> html#Macro-expansion
> if there were some hygienic caveit in my macro definitions , it would fail
> with Bigloo Scheme too,
> but it works as you can see in this ouput of logs, when running another
> portion of the code that use exactly the same debug macros, debug-macro is
> well defined (#t):
>
> Sidonie : ResultatMesuresF : postHandler : identificateur :N° BD
> BiglooCode.scm :: ResultatMesuresF :: debug-mode = #t
> BiglooCode.scm :: ResultatMesuresF :: nombreobjets = 0
> BiglooCode.scm :: ResultatMesuresF :: bstr_identificateur = N° BD
> BiglooCode.scm :: ResultatMesuresF :: bstr_objet = 56.130
> BiglooCode.scm :: ResultatMesuresF :: len_identificateur = 6
> BiglooCode.scm :: ResultatMesuresF :: (string? bstr_identificateur) = #f
> BiglooCode.scm :: ResultatMesuresF :: identificateur = N° BD
> BiglooCode.scm :: ResultatMesuresF :: (string? identificateur) = #t
> TEST N° BD
> TEST N° BD
> BiglooCode.scm :: ResultatMesuresF :: essai = TEST N° BD
> BiglooCode.scm :: ResultatMesuresF :: identificateur = N° BD
> BiglooCode.scm :: ResultatMesuresF :: (string? essai) = #t
> BiglooCode.scm :: ResultatMesuresF :: (string=? identificateur "" ) = #f
>
> Sidonie : DataBase : searchDriver : driver found
> Sidonie : DataBase : connectStatic : Hostname = moita.oca.eu
> Sidonie : DataBase : connectStatic : using localhost as computer name and
> mattei as user for sidonie database
> Sidonie : DataBase : connectStatic : connection established
> Sidonie : DataBase : createStatementStatic : done
>
> debug.scm : debug-display-nl : debug-mode = #t
> BiglooCode.scm :: ResultatMesuresF :: choixres =
> Ref
> debug.scm : debug-display-nl : debug-mode = #t
> BiglooCode.scm :: ResultatMesuresF :: (cond : Ref
> debug.scm : debug-display-nl : debug-mode = #t
>
> Damien
>
>
> On Tue, Oct 3, 2017 at 5:21 PM, Sudarshan S Chawathe <chaw@eip10.org>
> wrote:
>
>> I did not get a chance to look at your code carefully but, based on a
>> very quick look, I suspect that it may be running afoul of
>> syntactic-hygiene rules. In particular, I believe that the identifier
>> debug-mode used in the syntax-definitions of 'debug', etc., cannot refer
>> to the top-level debug-mode variable due to hygiene rules.
>>
>> Regards,
>>
>> -chaw
>>
>>
>
next prev parent reply other threads:[~2017-10-03 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 13:41 Damien MATTEI
2017-10-03 15:21 ` Sudarshan S Chawathe
2017-10-03 15:34 ` Damien Mattei
2017-10-03 15:35 ` Damien Mattei [this message]
2017-10-03 16:13 ` Per Bothner
2017-10-04 13:46 ` Damien MATTEI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADEOadeTNueSDEM-35E=Opbgzxtf_uO71SEtg6DvbeEbZD9zJA@mail.gmail.com' \
--to=damien.mattei@gmail.com \
--cc=kawa@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).