unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: compiler dep on r6rs
Date: Thu, 27 Jan 2011 11:55:36 +0100	[thread overview]
Message-ID: <m339oeipjr.fsf@unquote.localdomain> (raw)
In-Reply-To: <m3wrnleusr.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 07 Dec 2010 11:33:56 +0100")

On Tue 07 Dec 2010 11:33, Andy Wingo <wingo@pobox.com> writes:

> The new R6RS support is great. However we are currently pulling in (rnrs
> base) into the set of modules needed by the compiler, because (language
> assembly compile-bytecode) uses open-bytevector-output-port, and the
> ports impl gained a dep on base.
>
> Is there any way that we can remove this dependency? It will speed up
> bootstrap and the pause as the first expression at the REPL is
> compiled.

How about we move most of the procedures that are defined in C via
scm_init_r6rs_ports to (ice-9 binary-ports).  Then (rnrs io ports) can
still be a r6rs module, and low-level code can avoid pulling in r6rs.

I plan to do this soonish if there are no objections.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-01-27 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 10:33 compiler dep on r6rs Andy Wingo
2011-01-27 10:55 ` Andy Wingo [this message]
2011-01-27 13:28   ` Ludovic Courtès
2011-01-27 14:07     ` Andy Wingo
2011-01-27 19:36       ` Ludovic Courtès
2011-02-20 21:46   ` 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=m339oeipjr.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).