unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Wolfgang J Moeller <wjm@heenes.com>
Cc: bug-guile@gnu.org
Subject: Re: {debug,read,readline,print}-{set!,disable,enable}
Date: Fri, 20 May 2011 11:57:04 +0200	[thread overview]
Message-ID: <m3zkmhwv7z.fsf@unquote.localdomain> (raw)
In-Reply-To: <alpine.LNX.2.00.1104291200360.12740@gwdw03.gwdg.de> (Wolfgang J. Moeller's message of "Fri, 29 Apr 2011 14:12:11 +0200 (CEST)")

On Fri 29 Apr 2011 14:12, Wolfgang J Moeller <wjm@heenes.com> writes:

> In fact, {debug,print,read}-set! are macros that want "option-name" to
> be a literal symbol, while {debug,read}-{en,dis}able are procedures
> indeed (apparently taking multiple arguments) that want the
> "option-name"[s] to be quoted symbol[s].

Indeed; nasty, but it's what we've got.  Fixed the docs.

> [Noticed while looking for something like V1 (debug-disable 'debug)
> that might speed up execution.]

It's spelled `--no-debug'; see "Invoking Guile".

  `--debug'
       Start with the debugging virtual machine engine.  Using the
       debugging VM will enable support for VM hooks, which are needed
       for tracing, breakpoints, and accurate call counts when profiling.
       The debugging VM is slower than the regular VM, though, by about
       10 percent.  *Note VM Hooks::, for more information.

       By default, the debugging VM engine is only used when entering an
       interactive session.  When executing a script with `-s' or `-c',
       the normal, faster VM is used by default.

  `--no-debug'
       Do not use the debugging VM engine, even when entering an
       interactive session.

Also note that git is about 10-20% faster than 2.0.1.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-05-20  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 13:05 shift and reset, plus "while" Wolfgang J Moeller
2011-04-13  9:47 ` Andy Wingo
2011-04-13 14:56   ` [shift and reset, plus] "while" Wolfgang J Moeller
2011-04-13 15:41     ` Andy Wingo
2011-04-13 17:31       ` Wolfgang J Moeller
2011-04-28 12:15         ` Andy Wingo
2011-04-29 12:12           ` {debug,read,readline,print}-{set!,disable,enable} Wolfgang J Moeller
2011-05-20  9:57             ` Andy Wingo [this message]
2011-05-22 11:53               ` {debug,read,readline,print}-{set!,disable,enable}, etc Wolfgang J Moeller
2011-06-17 16:09                 ` Andy Wingo
2011-04-13 15:17 ` shift and reset, plus "while" Mark H Weaver
2011-04-28 11:10 ` Andy Wingo
2011-04-28 14:44   ` Wolfgang J Moeller

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=m3zkmhwv7z.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=wjm@heenes.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).