cond-expand for separating compiled and interpreted code
Hi all, Is there a `cond-expand` feature only available when compiling with `gsc`, or vice-versa, when interpreting with `gsi`? Cheers, -- -alex http://unendli.ch/
Afficher les réponses par date
Not sure if this applies, but https://mercure.iro.umontreal.ca/pipermail/gambit-list/2012-April/005917.htm... http://billsix.github.io/bug#_at_compile_time On Fri, May 25, 2018, 4:17 AM Alex Queiroz <asandroq@gmail.com> wrote:
Hi all,
Is there a `cond-expand` feature only available when compiling with `gsc`, or vice-versa, when interpreting with `gsi`?
Cheers, -- -alex http://unendli.ch/ _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Hi Alex. Alex wrote on 2018-05-25 10:16:
Is there a `cond-expand` feature only available when compiling with `gsc`, or vice-versa, when interpreting with `gsi`?
I found the definition of generate-cond-expand-features in lib/_nonstd.scm . There does not seem to be cond-expand feature identifier that you can use. Maybe it makes sense to introduce gambit-gsc (or gambit-compiler) and gambit-gsi (or gambit-interpreter) ? Ciao Sven
participants (3)
-
Alex Queiroz -
Bill Six -
Sven Hartrumpf