[Coco] Coco Digest, Vol 143, Issue 69

[Stephen Pereira]

Hi Manney,

I tried attaching the code to my first message, but that didn’t work.

Can you tell me how to upload the file, and to where?  Otherwise, I can just send it to your e-mail address.

Thanks!
smp
--
Stephen M. Pereira
Bedford, NH  03110
KB1SXE

> ------------------------------
> 
> Message: 5
> Date: Sat, 15 Nov 2014 21:37:24 +0000
> From: Aaron <manney at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Subject: Re: [Coco] [CoCo] Re: Basic Lisp
> Message-ID:
> 	<CAARQjFNW6g4Lc3JJFu7R=uvTonFoXxpx5ZVwFadGdDNyHKwNYQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> 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.
> 
>