Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!udel!rochester!kodak!ispd-newsserver!uucp From: amusing!lordbah@bisco.kodak.COM (Lord Bah) Newsgroups: comp.sys.amiga Subject: Re: SAS C 5.10 problems Message-ID: <9011301521.AA06821@bisco.kodak.COM> Date: 30 Nov 90 03:06:16 GMT Sender: news@ssd.kodak.com Reply-To: amusing!lordbah@bisco.kodak.COM Followup-To: comp.sys.amiga Organization: Eastman Kodak Lines: 30 Originator: uucp@bisco Return-Path: Doug Walker says: > In article <9011081128.AA14500@bisco.kodak.COM> nobody@Kodak.COM writes: ^^^^^^ Well, yeah, that's what it said, but I put my real address in the signature... > >Since it would take me days to figure out how to get back to a CBM > >shell, > > Why would it take you 'days'? What's wrong with "NewShell"? There > have been MANY reports of problems with AShell, not just with the > compiler. I recommend looking at WShell from Bill Hawes. "NewShell" gives me an AShell. I think going back to CBM shell would mean fiddling with shell-seg or whatever it is, newshell, newcli, and who knows what else. Not to get into religious shell discussions, I'll just say I've never seen any other problem with AShell. I'd be interested in any bug list. > You have to link with the floating point libraries if you use any > floating point variables. Thanks. Also thank you to the many people who have responded thus to me in email. This was indeed the problem. -------------------------------------------------------------------- Jeff Van Epps amusing!lordbah@bisco.kodak.com lordbah@cup.portal.com sun!portal!cup.portal.com!lordbah