Hi, Alex.
This sounds fun!
> - re rat: just humour me on this, it's a temporary name anyway, until the
> full deployment of the project, which incidentally, is the Racket port of
> scmutils
> - following from the above, so yes, it will certainly have to be a #lang, no
> questions there.
Apologies if I missed this from an earlier message or thread, but:
What feature or aspect of scmutils means it will need to be
implemented as a Racket language?
AFAIK MIT Scheme doesn't have anything like #lang, so I'm surprised.
I recall some mention of scmutils using MIT Scheme application hooks.
But AFAICT this is equivalent to Racket's `prop:procedure`. That is,
you can can define `struct`s that are applicable like procedures. On a
shallow read, it even looks like prop:procedure has both variants of
MIT Schemes' application hooks ("apply hooks" and "entities")?
So: If one reason for doing a lang was to define your own #%app -- you
probably don't need to.
Is there something else?
> Ho hum, I see there is probably no other way, I'll have to upload. I'll let
> you know soon as I do. That way, more issues can be raised on github too,
> amongst those interested and contribute to less noise on this list.
That would probably help a lot!
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
