From: Richard S. Hall on 28 Sep 2006 07:53 "Pascal Bourguignon" <pjb(a)informatimago.com> wrote in message news:87fyecwfes.fsf(a)thalassa.informatimago.com... > Petter Gustad <newsmailcomp6(a)gustad.com> writes: > >> George Neuner <gneuner2/@comcast.net> writes: >> >>> Aztec had a good quality rommable code K&R C compiler for the 6502. >>> IIRC, it was based on a prior 6800 version. >> >> The 1979 August issue of Byte Magzine had an article on a Lisp >> implementation for the 6800. > > Key word being "a". But indeed, if I had a lisp on my 6809 instead of > Pascal, I would probably have had more fun :-) > > -- > __Pascal Bourguignon__ http://www.informatimago.com/ > > "Our users will know fear and cower before our software! Ship it! > Ship it and let them flee like the dogs they are!" Nothing like the "good 'ol days" of using Mark Williams C compiler to write rommable Z80 code on Zenith Z100, then split into pieces to be put on 2716 (EPROM)s. The compiler was buggy, you had to check the assembly code: "int x; x = 1;" worked fine, but "int x = 1;" would not complain in the compiler but leave x uninitialized! There were other bugs too. Of course you could connect the end result to a 300 baud modem and use ITS/MacLisp!. Sorry if I sent to your email Pascal - hit wrong button meant to send to group!
From: GP lisper on 28 Sep 2006 08:22 On Thu, 28 Sep 2006 00:55:38 -0400, <gneuner2/@comcast.net> wrote: > > OTOH, I have eerily similar memories of writing my first PC programs > using Microsoft C on a 640KB machine with dual 360KB floppy drives. > Except in the PC case, the compiler took 2 (compiler) disk swaps per > source file and another disk swap to link and I couldn't load any of > it into a ram disk. You were getting killed by the floppies, 5in floppies were slow. I ran this sort of stuff in a 1.2 meg ramdisk, mapped into the BIOS as a disk drive...and it was 'Microsoft'. -- Reply-To email is ignored. -- Posted via a free Usenet account from http://www.teranews.com
First
|
Prev
|
Pages: 1 2 3 4 5 6 7 Prev: Clipboard Access on Windows Next: a potential lisp convert, and interpreting the shootout |