From: Andy Wingo <wingo@pobox.com>
To: Mark Harig <idirectscm@aim.com>
Cc: guile-devel@gnu.org
Subject: Re: Patch: New section "Invoking Guile" for chapter "Programming in Scheme"
Date: Sun, 24 Apr 2011 23:00:16 +0200 [thread overview]
Message-ID: <m37hajbc0v.fsf@unquote.localdomain> (raw)
In-Reply-To: <8CDD0D662A18273-1820-10289@webmail-m029.sysops.aol.com> (Mark Harig's message of "Sun, 24 Apr 2011 16:36:12 -0400")
Hi Mark,
Thanks for the revisions.
On Sun 24 Apr 2011 22:36, Mark Harig <idirectscm@aim.com> writes:
> On Sun, Apr 24, 2011 at 04:33:44PM +0200, Andy Wingo wrote:
>> your patches should be "atomic"
>
> "3. No patch introduces a regression: after applying any
> initial part of the series, the resulting project still
> compiles and works, and has no bugs that it didn’t have
> before."
Right, at the end of applying all of your patches, I'm sure that's the
case; however the first patch adds an @include without adding the
appropriate file, so applying just the first patch without the following
two would yield a project that doesn't compile. I just meant that you
need to squish the first two or three of them together. I can do that
when I apply them, though.
By @itemx I just meant to do instead of:
> +@item -s @var{script} @var{arg...}
you would
@item @var{script} @var{arg...}
@itemx -s @var{script} @var{arg}
The other option would be
@item [-s] @var{script} @var{arg}
which is not as clear IMO. I feel that it's important to have a good
example up there, and making it clear that it's OK to just invoke Guile
as "guile foo.scm" is important. But your description is good too.
> +For compatibility with some versions of Guile 1.4, you can also use the
> +form @code{(symbol ...)} (that is, a list of only symbols that doesn't
> +start with @code{@@}), which is equivalent to @code{(@@ (symbol ...)
> +main)}, or @code{(symbol ...) symbol} (that is, a list of only symbols
> +followed by a symbol), which is equivalent to @code{(@@ (symbol ...)
> +symbol)}. We recommend to use the equivalent forms directly since they
> +correspond to the @code{(@@ ...)} read syntax that can be used in
> +normal code. See @ref{Using Guile Modules} and @ref{Scripting
> +Examples}.
Again, probably worth eliding the deprecated 1.4 stuff...
> +@item --auto-compile
> +Compile source files automatically (default behavior).
> +
> +@vnew{2.0}
> +
> +@item --no-auto-compile
> +Disable automatic source file compilation.
> +
> +@vnew{2.0}
Need --fresh-auto-compile here too
> +@item GUILE_AUTO_COMPILE
> +@vindex GUILE_AUTO_COMPILE
Need to note GUILE_AUTO_COMPILE=fresh, and @ref to Compilation
Best regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-04-24 21:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 19:46 Patch: New section "Invoking Guile" for chapter "Programming in Scheme" Mark Harig
2011-04-24 14:33 ` Andy Wingo
2011-04-24 20:36 ` Mark Harig
2011-04-24 21:00 ` Andy Wingo [this message]
2011-04-24 21:58 ` Mark Harig
2011-04-25 8:01 ` Andy Wingo
2011-04-24 22:09 ` David Pirotte
2011-04-24 22:43 ` Indexing Scheme and C identifiers separately Mark Harig
2011-04-25 1:18 ` Noah Lavine
2011-04-25 16:16 ` David Pirotte
2011-05-20 22:53 ` Neil Jerram
2011-04-25 19:49 ` Patch: New section "Invoking Guile" for chapter "Programming in Scheme" Mark Harig
2011-04-26 18:07 ` Neil Jerram
2011-04-26 21:01 ` Ludovic Courtès
2011-04-27 9:40 ` Andy Wingo
2011-04-27 10:23 ` Ludovic Courtès
2011-04-27 19:29 ` Neil Jerram
2011-04-27 16:54 ` Mark Harig
2011-04-27 19:40 ` Neil Jerram
2011-06-30 11:23 ` Andy Wingo
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=m37hajbc0v.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=idirectscm@aim.com \
/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).