[Coco] [CoCo] Re: Basic Lisp

[J Arcane]

Just to update, re: my previous post, Heresy is working now. You'll need
Racket installed to run it, but there's instructions and brief function
docs on the Github now: https://github.com/jarcane/heresy

On Sun, Nov 16, 2014 at 11:35 AM, J Arcane <jarcane at gmail.com> wrote:

> It's on Github at https://github.com/jarcane/heresy but it doesn't quite
> work at the moment and I've yet to write proper docs for it. I've got most
> of the important syntax defined now, and you can load it and run stuff with
> them in the REPL, but I haven't been able to get it working as a library or
> #lang module, and I'm having a hell of a time figuring out why.
>
> On Sat, Nov 15, 2014 at 11:37 PM, Aaron <manney at gmail.com> wrote:
>
>> On Sat, Nov 15, 2014 at 8:34 PM, J Arcane <jarcane at gmail.com> wrote:
>>
>> > Wow! Nice work. Debugging old-school BASIC is rarely the most painless
>> > experience, so kudos to your efforts.
>> >
>> > I've been working on a little language project myself, writing a
>> > BASIC-inspired Lisp dialect as a Racket library. It's presented me with
>> any
>> > number of odd conundrums and important revelations about how certain
>> things
>> > work and the differences between languages.
>> >
>> > The most weird one though, and one I am still a bit stuck on is the
>> > PRINT/INPUT commands vs. their Lisp eqvs. and how to define them.
>> BASIC's
>> > PRINT more or less roughly aligns to displayln, with some extra syntax
>> like
>> > the ; and , shortcuts, and INPUT really doesn't have an equivalent at
>> all
>> > exactly (owing largely to major differences in how the two languages do
>> > things). Lisp uses read and read-line, and lacks strict typing (though
>> > there are variants for reading a string or chars specifically), nor is
>> it
>> > even explicitly required to be assigning to a variable; they're simply
>> > functions that take some input from a given port, and return that input.
>> >
>> > It's a case of two very, very different approaches and needing to decide
>> > which one to prioritize. Not getting far yet.
>> >
>>
>> Do you have any code up anywhere?  I doubt I'd be any help at this stage,
>> but curious how you're doing things.
>>
>> I've been kinda looking at TinyScheme, wondering if it (or it's
>> predecessor, MiniScheme) would be a good CoCo fit.
>>
>> -M.
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>
>