From: "Orians, Jeremiah (DTMB)" <OriansJ@michigan.gov>
To: Mark H Weaver <mhw@netris.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"bootstrappable@freelists.org" <bootstrappable@freelists.org>
Subject: RE: [bootstrappable] Re: prototyping the full source bootstrap path
Date: Mon, 27 Nov 2017 12:42:50 +0000 [thread overview]
Message-ID: <SN1PR09MB0959DA5DB7B6BDD66669D477C6250@SN1PR09MB0959.namprd09.prod.outlook.com> (raw)
In-Reply-To: <87a7zdmw3m.fsf@netris.org>
> Jan is correct that Guile is still heavily tied to its C code. It's true that Guile's compiler is written in Scheme and that
> the C evaluator is used only during bootstrapping, but the C bootstrap evaluator is only a small piece of libguile.
> The majority of libguile is still needed. Notably, the entire runtime, the VM, and implementations of many data
> structures and other libraries are written in C.
Thank you for correcting my mistaken assumption.
next prev parent reply other threads:[~2017-11-27 12:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 22:31 prototyping the full source bootstrap path Jan Nieuwenhuizen
2017-11-20 9:20 ` [bootstrappable] " Ludovic Courtès
2017-11-20 11:42 ` [bootstrappable] " Ricardo Wurmus
2017-11-20 18:41 ` Jan Nieuwenhuizen
2017-11-20 18:48 ` Orians, Jeremiah (DTMB)
2017-11-20 21:55 ` Ludovic Courtès
2017-11-21 12:59 ` Orians, Jeremiah (DTMB)
2017-11-21 17:52 ` Jan Nieuwenhuizen
2017-11-21 18:23 ` Orians, Jeremiah (DTMB)
2017-11-23 4:56 ` Mark H Weaver
2017-11-27 12:42 ` Orians, Jeremiah (DTMB) [this message]
2017-11-23 17:55 ` Jan Nieuwenhuizen
2017-11-23 22:12 ` Ricardo Wurmus
2017-11-25 10:51 ` Jan Nieuwenhuizen
2017-11-20 18:48 ` Jan Nieuwenhuizen
2017-11-20 19:22 ` Gábor Boskovits
2017-11-20 12:45 ` [bootstrappable] " Orians, Jeremiah (DTMB)
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN1PR09MB0959DA5DB7B6BDD66669D477C6250@SN1PR09MB0959.namprd09.prod.outlook.com \
--to=oriansj@michigan.gov \
--cc=bootstrappable@freelists.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).