From: Mike Bushroe <mbushroe@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: on bootstrapping: introducing Mes
Date: Tue, 21 Jun 2016 11:44:59 -0700 [thread overview]
Message-ID: <CA+CyYa34+GoAbFi-1nG5PxPWp9YqRzShpyXS8S7Ph=Nv2dw2Kg@mail.gmail.com> (raw)
In-Reply-To: <87porasc67.fsf@gnu.org>
On Tue, Jun 21, 2016 at 10:07 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> Mike Bushroe writes:
>
> Hi!
>
> Ah sorry, not exactly. I intend to write the initial LISP interpreter
> in binary/hex...the current implementation in C is only intended to be
> an intermediate stage in the development process, i.e., to figure out
> what exactly is needed as a minimal interpreter. Experimenting using C
> is easier than in assembly and close enough to make change to assembly
> later.
>
> Greetings,
> Jan
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
>
Jan,
I think I better understand what you are working on now. The vest-pocket
assembly code bootstrap is a great idea for getting Scheme working where
Scheme has never been before. But it may limit the bootstrapping to only
X86 based machines. While the majority of users will be installing onto
that, you might consider something that supposedly is more universal.
Something like Java that is supposed to be available for almost everything
from small embedded systems to the latest and greatest CPUs and OSs. It
would also be a smaller change than C to assembler although is truly very
close to assembler on a good CPU. On the other hand Java is 'yet another
language' and one I have not worked with yet myself. I have done some
assembly programming, even on X86 based machines.
I enjoyed the compiler course at the university and it sounds like you
are having fun here. And since I never really got a feel for LISP let alone
Lambda functions I doubt I will have any further suggestions that would be
helpful. You are already getting to beyond what I have experience with.
Mike
--
"Creativity is intelligence having fun." — Albert Einstein
next prev parent reply other threads:[~2016-06-21 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 11:08 on bootstrapping: introducing Mes Jan Nieuwenhuizen
2016-06-20 17:47 ` Mike Bushroe
2016-06-21 17:07 ` Jan Nieuwenhuizen
2016-06-21 18:44 ` Mike Bushroe [this message]
2016-06-21 14:32 ` Ludovic Courtès
2016-06-21 16:36 ` Jan Nieuwenhuizen
2016-06-21 20:38 ` Ludovic Courtès
2016-06-26 21:17 ` Amirouche Boubekki
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='CA+CyYa34+GoAbFi-1nG5PxPWp9YqRzShpyXS8S7Ph=Nv2dw2Kg@mail.gmail.com' \
--to=mbushroe@gmail.com \
--cc=guile-user@gnu.org \
--cc=janneke@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).