From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: conditional code segments
Date: Fri, 1 Jun 2018 19:34:23 -0700 [thread overview]
Message-ID: <7c307320-d51b-231c-9978-320989fc7641@gmail.com> (raw)
In-Reply-To: <87d0xadk8b.fsf@netris.org>
On 06/01/2018 06:56 PM, Mark H Weaver wrote:
> Hi Matt,
>
> Matt Wette <matt.wette@gmail.com> writes:
>
>> In C I can use `#ifdef' .. `#endif' to "comment out" code segments.
>>
>> In Scheme, one can use `#|' and '|#' which is OK but requires dealing with both ends of the
>> segment to switch on / off. And emacs (v 24.5) scheme mode does not always fontify the buffer
>> correctly with #|...|#.
> There's another kind of comment in standard Scheme (both R6RS and R7RS)
> that's supported by Guile, but unfortunately it doesn't seem to be
> documented in our manual. Simply put the two characters "#;" before any
> datum, and the entire datum will be skipped by the reader. Whitespace
> may appear between "#;" and the datum. So, for example:
>
> #;
> (let ()
> ...)
>
> will cause the entire 'let' form (which is a datum) to be skipped.
> Emacs and paredit understand this syntax, and will act accordingly.
>
> It works not only at top-level, but also nested arbitrarily deeply
> within datums. So, for example:
>
> scheme@(guile-user)> (let ()
> (display "1\n")
> (display "2\n")
> #;
> (display "3\n"))
> 1
> 2
> scheme@(guile-user)>
>
> and if you put that code in an Emacs buffer in Scheme mode, the
> (display "3\n") will be colorized as a comment, but the final closing
> parenthesis will have the default color.
>
I use #; a lot. So for large number of forms then #;(begin ...) should work.
And I didn't know white space can separate the #; from the Scheme form. Cool.
> I tried using cond-expand but it does not work as expected:
> scheme@(guile-user)> (cond-expand-provide (current-module) '(abc))
> $1 = (abc)
> scheme@(guile-user)> (cond-expand (abc #t))
> While compiling expression:
> Syntax error:
> unknown file:2:0: cond-expand: unfulfilled cond-expand in form (cond-expand (abc #t))
> It didn't work because when a 'cond-expand' form is used in module FOO,
> it looks for the features (e.g. 'abc') in all of the modules that are
> imported by FOO, but not in FOO itself.
Thanks much.
prev parent reply other threads:[~2018-06-02 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 23:37 conditional code segments Matt Wette
2018-06-02 1:11 ` Alex Vong
2018-06-02 1:56 ` Mark H Weaver
2018-06-02 2:34 ` Matt Wette [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c307320-d51b-231c-9978-320989fc7641@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@gnu.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).