Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!diku!seindal
From: seindal@diku.UUCP (Rene Seindal)
Newsgroups: comp.lang.c++
Subject: Re: Re: Re: Cornell V1.2 Bug Report (1/5)
Message-ID: <3245@diku.UUCP>
Date: Wed, 27-May-87 11:54:17 EDT
Article-I.D.: diku.3245
Posted: Wed May 27 11:54:17 1987
Date-Received: Sat, 30-May-87 02:23:59 EDT
References: <3237@diku.UUCP> <2816@cit-vax.Caltech.Edu>
Organization: DIKU, U of Copenhagen, DK
Lines: 46

In article <2816@cit-vax.Caltech.Edu> jon@oddhack.caltech.edu (Jon Leech) writes:
>In article <3237@diku.UUCP> seindal@diku.UUCP (Rene Seindal) writes:
>>This is actually one of the nastiest bugs in CC under Berkeley UNIX, since
>>one can't bring up the system before it is fixed.  I think Bjarne should be
>>aware of such sysV dependencies for the next release.  As far as I could
>>see, the distribution (of 1.2) could not run on anything but sysV.  This is
>>not acceptable for a commercially distributed system.

>	I don't know about 1.2, but my 1.1 manual says prominently on the
>front cover:

>	UNIX System V
>	AT&T C++ Translator
>	Release Notes

>and also comments that it is intended for System V in the Introduction.
>This is hardly surprising given AT&T's position with respect to Sys V!

I don't have any release notes for 1.2.1, but the label on my
distribution tape says

	UNIX* System
	C++ Translator Release 1.2.1

I have a C++ Translator Porting Guide, and it contains a lot of useful
hints about how to port C++ to BSD.  But all these information
concerns cfront, munch and the system header files.  Nothing is said
about the CC script (except about putting a "#!/bin/sh" in top of it,
which is trivial)

>If you want support for BSD, buy it from one of the outfits that repackages 
>it. Otherwise, you takes what you can get. Having some experience with
>keeping a program portable across many types of unix and other operating
>systems (a complex screen editor in my case), I have a great deal of 
>sympathy for Bjarne. Give him a break.

If is wasn't for the basename bug,  C++ would have been extremely easy
to port, and I could have done it in an hour.  Because of this bug, it
took me more than a day.  When it was it was fixed everything was fine.

About all the problems I have encountered with C++, concerns the CC
script.  It seems as if it was forgotten when working through the
portablity issues.  

Rene' Seindal (seindal@diku.UUCP).
The Computer Department, Institute of Datalogy, U. of Copenhagen.