> On Apr 27, 2017, at 5:55 AM, Jan Nieuwenhuizen wrote:
>
>
> [cc: Matt, author of Nyacc]
>
>> Well now you could have told them we already had the forth
>> https://github.com/oriansj/stage0/blob/master/stage2/forth.s
>> but none of the people in the forth community bothered to build upon it
>
[cc: Matt, author of Nyacc]
> Well now you could have told them we already had the forth
> https://github.com/oriansj/stage0/blob/master/stage2/forth.s
> but none of the people in the forth community bothered to build upon it
You created a fully bootstrappable LISP and FORTH, wow!
That would ma
I am pleased to announce the release of Mes 0.5, representing 249
commits over 4 months. Mes is now self-hosting, or rather it features
a mutual self-hosting Scheme interpreter and C compiler: mes.c and
mescc; a Nyacc-based C compiler backend that also works separately
with Guile.
* About
M
Jan Nieuwenhuizen :
> Christopher Allan Webber writes:
>
>> I've noticed that it's common in Guile modules to use "foo?" for
>> variable names involving booleans. It's tempting,
>
>> But is it a good idea?
>
> It's an idea that I like and use.
There are also the traditional:
(let ((name$ "He
2017-04-27 12:39 GMT+02:00 Jan Nieuwenhuizen :
> Christopher Allan Webber writes:
>
> > I've noticed that it's common in Guile modules to use "foo?" for
> > variable names involving booleans. It's tempting,
>
> > But is it a good idea?
>
> It's an idea that I like and use. Not sure that says any
Christopher Allan Webber writes:
> I've noticed that it's common in Guile modules to use "foo?" for
> variable names involving booleans. It's tempting,
> But is it a good idea?
It's an idea that I like and use. Not sure that says anything about
good or bad.
I would like to help you paint thou
