Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!stanford.edu!neon.Stanford.EDU!pescadero.Stanford.EDU!philip
From: philip@pescadero.Stanford.EDU (Philip Machanick)
Newsgroups: comp.sys.mac.system
Subject: Re: MacinTalk
Keywords: MacinTalk
Message-ID: <1991Jun1.050959.28883@neon.Stanford.EDU>
Date: 1 Jun 91 05:09:59 GMT
References: <1991May29.085135.12717@netcom.COM> <1991May31.233024.17115@m.cs.uiuc.edu>
Sender: news@neon.Stanford.EDU (USENET News System)
Reply-To: philip@pescadero.stanford.edu
Organization: Stanford University
Lines: 19

In article <1991May31.233024.17115@m.cs.uiuc.edu>, gillies@m.cs.uiuc.edu (Don Gillies) writes:
|> jkatz@netcom.COM (Joseph Katz) writes:
|> >>MacinTalk was done by an outside firm, 
|> 
|> >  TRUE.  MacinTalk was written by myself and Mark Barton.  Apple contacted
|> >         us back in late 1983 to write a speech synthesizer for the yet to
|> >         be released Mac.
|> 
|> It is a pity you have not pursued macintalk as an independent product.
|> It seems plausible that you could update and/or improve macintalk and
|> market it yourselves, in many different ways.
[5 ideas deleted]
6. A talking debugger. Some of my students once used MacinTalk
for of debugging output. It was great fun - they could
tell what their program was doing without having to mess up
the screen.
-- 
Philip Machanick
philip@pescadero.stanford.edu