Newsgroups: comp.lang.lisp.x
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!portc02.blue.aol.com!howland.erols.net!worldnet.att.net!hunter.premier.net!news.lightlink.com!mv!usenet
From: David Betz <dbetz@xlisper.mv.com>
Subject: Re: David: How much did AutoDESK pay?
Content-Type: text/plain; charset=us-ascii
Reply-To: dbetz@xlisper.mv.com
Content-Transfer-Encoding: 7bit
Organization: MV Communications, Inc.
Message-ID: <32E76595.3757@xlisper.mv.com>
References: <32D69578.11A7@xlisper.mv.com> <5bo1ph$oab@bagan.srce.hr> <32E029ED.E1D@xlisper.mv.com> <32e63aff.111081106@news.sime.com>
X-Mailer: Mozilla 3.01 (Win95; I)
Mime-Version: 1.0
X-Nntp-Posting-Host: xlisper.mv.com
Date: Thu, 23 Jan 1997 13:20:21 GMT
Lines: 36

Reini Urban wrote:

> Could you tell me how much AutoDESK paid for licensing xlisp?
Nothing.  They used an early version that didn't contain a copyright
notice without asking permission or offering to pay a license fee.
Since there was no copyright notice, I don't think I can really complain
much.  I was more irritated that they didn't give me credit as the
original author.  I mentioned that to them a while back and that's when
they added a reference to XLISP and me to their AutoLISP manual.  I
don't know if it is still there.

> Was xlisp 1.5 ever released to the public?
Yes.  All versions of XLISP since 1.1 were released to the public with
the restriction that they not be used for commercial applications
without permission.

> Did you understand why they did not implement 80% of your features?
They started with version 1.0 or 1.1.  As far as I know, they *did*
implement all of the features in that version.

> Do they still own the sources?
They have never owned the sources.  I own the sources.

> I'm asking this because I'm wondering why they did not already added
> some functionality after getting rid of the memory problems with
> AutoCAD R10c10.
I offered to help them upgrade to a newer version of XLISP a while back
but they weren't interested.  They said they wanted to downplay AutoLISP
in favor of their C API.  I'm surprised that AutoLISP is still part of
their product based on what they said at the time.

-- 
David Betz
DavidBetz@aol.com
dbetz@xlisper.mv.com
(603) 472-2389
