Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: Sun documentation
Message-ID: <7642@mimsy.UUCP>
Date: Wed, 22-Jul-87 07:13:19 EDT
Article-I.D.: mimsy.7642
Posted: Wed Jul 22 07:13:19 1987
Date-Received: Fri, 24-Jul-87 02:51:13 EDT
References: <608@zen.UUCP> <2299@hoptoad.uucp> <21211@sun.uucp> <830@omepd> <1499@ncc.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 25

>In article <23262@sun.uucp>, guy%gorodish@Sun.COM (Guy Harris) writes:
>>(Besides, getting [pre-troffed documentation] wouldn't do you any good;
>>we use our own macro packages and other tools, and it would be too
>>much trouble to supply and support them.)

In article <1499@ncc.UUCP> lyndon@ncc.UUCP (Lyndon Nerenberg) writes:
>... If you use your own macro packages to produce the doc
>then they (the macros) already exist, so there is no (non-politcol)
>reason that they can't be shipped with the troff source.

True.

>Nobody says you have to support the macro package.

I think experience tends to prove otherwise:  Some customers complain
about bugs in things released as `unsupported'.  This is no one's
fault but said customers'; these people make things harder for
everyone by tending to convince companies not to ship unsupported
tools.

(Moral:  If you get something that says `unsupported' and it does
not work, keep quiet. :-) )
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris