Re:Mal Lisp for TempleOS
by bagnalla on Sunday December 03, 2017 @09:02PM
(#15840954)
HolyC is great -- default arguments and built-in exception handling are big pluses over C. There are a few shortcomings, though, such as the lack of short-circuiting logical operators and some unfortunate behavior related to variable declarations within nested scopes (just avoid doing that IMO).
[ Parent
| on HN ]
Re:Mal Lisp for TempleOS
by andyjohnson0 on Monday December 04, 2017 @07:38AM
(#15843379)
> lack of short-circuiting logical operators
I'm curious about the reason for this - does anyone know why they were implemented this way?
Probably because God commanded it.
You are being downvoted but many many times have I asked a question regarding templeos and that is the actual answer
The issues can probably be fixed by writing a bit of a better compiler, HolyC2 maybe?
I've thought about using this Lisp interpreter to bootstrap a compiler for a new language, probably targeting HolyC. If someone were to write some decent lexer/parser generator tools in HolyC it would go a long way in making something like that possible.
Call it Protestant.
Re:Mal Lisp for TempleOS
by breakingcups on Monday December 04, 2017 @03:19AM
(#15842427)
Alternatively, HolyC++ or HolyD.
HolyMoly, duh.
Ideally a HolyC++ would be able to compile normal HolyC without any changes to the source while also adding new stuff and while not being C++ in the process. That all would be very neat.