Article View: comp.sys.next.software
Article #524Re: Allegro CL 3.1.20 fix for 3.0
From: Jack &
Date: Thu, 10 Sep 1992 06:34
Date: Thu, 10 Sep 1992 06:34
51 lines
2836 bytes
2836 bytes
In article <1992Sep2.095958.15685@ads.com> bvrotney@ADS.COM (Bill Vrotney) writes: > > Recall the anonymous fellows that claimed they have a fix for Allegro > CL 3.1.20 so that it will run under NeXTstep 3.0. I asked them to run the > Calculator example to verify that the fix works. Well they did and > discovered that although the base Lisp Works the Objective C interface did > not. I asked them to send me the fix anyway. If they do send me the fix with > permission I will post it here. > > I also talked with Franz and apparently whether or not the Objective C > interface will still be supported in Allegro 4.1 is still up in the air. You > can gripe about this by email or phone to: > > > Mike Margulies > Franz Inc. > mjm@franz.com > 510-548-3600 > > -- > Bill Vrotney > Advanced Decision Systems Well, between NeXT and Franz, the Common Lisp crowd has certainly been screwed over the past year. First, NeXT unbundled Common Lisp but said that they would support it. Many of us griped and got them to provide Common Lisp for original cube purchasers. Little did we know that it would be fine as long as we didn't need to interface with Object C in the interface builder. What good is a language that doesn't have access to the graphic primitives? So NeXT screwed us first. Then Franz decided that the only way for us to upgrade to their new and improved version of Allegro was for us to buy software support. Hey, that was over a year ago. Then THEY decided that they didn't want to support the NeXT and started backing out on existing accounts. Did anyone hear of a refund? Did anyone hear anything? Did anyone ask WHAT Franz had done to correct the problem, or WHY? Of course we did, and you do not want to hear their slimy response. Now I guess Franz and NeXT are vieing for who can screw the Lisp community the most, or the best. I for one am not impressed, and I would recommend going WAY over Mike Margulies' head. He is red tape, put there to avoid having to answer embarassing questions like why 4.0 wasn't ported to 3.0 when the beta came out. Sun was first, and then some other big ticket company. Forget the people who paid for software support simply to get their upgrades on the NeXT. Couldn't be that many people could it? Tired of hype and babbletalk, Jack Hodges San Francisco State University
Technical Details
Message-ID:
<1992Sep10.063407.231@csus.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!wupost!csus.edu!newsReferences:
<1992Sep2.095958.15685@ads.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.software Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!csus.edu!news From: hodges@huckleberry.sfsu.edu (Jack &) Subject: Re: Allegro CL 3.1.20 fix for 3.0 Message-ID: <1992Sep10.063407.231@csus.edu> Sender: news@csus.edu Reply-To: hodges@huckleberry.sfsu.edu Organization: California State University, Sacramento References: <1992Sep2.095958.15685@ads.com> Date: Thu, 10 Sep 1992 06:34:07 GMT Lines: 51