Path: utzoo!attcan!uunet!wuarchive!emory!hubcap!svissag
From: svissag@hubcap.clemson.edu (Steve L Vissage II)
Newsgroups: comp.lang.c
Subject: Turbo C Librarian
Message-ID: <11226@hubcap.clemson.edu>
Date: 29 Oct 90 17:14:59 GMT
Organization: Clemson University, Clemson, SC
Lines: 69

Hello, everyone.  I'm the author of the original post about turbo c.


>Gee, I REALLY hope I can help you...
>
>You're really an a$$hole, posting a message to a world-wide newsgroup,
>the subject of which is the C language (NOT SPECIFIC C COMPILERS OR
>LINKERS), publicly stating that you are having a problem using pirated
>software.

I do not recall saying that.  What I said was, "I have Turbo C, but none
of the documentation that goes with it."  While this is not entirely
accurate, it is much easier than an honest-to-god explanation, but if
you want one, read on.
 
I don't have a PC.  The Turbo C belongs to my Uncle.  When I discovered
he had it, I happened to be trying to learn C.  I started using his TC.
He has all the electronic documentation, which I have read, but it doesn't
explain TLIB well enough.  As I explained in e-mail to someone who was
nice enough to ASK if I had a pirated copy before he either helped me or
flamed me, I didn't want to write to you and say, "I read it, but I'm too
damn stupid to figure it out."  I was in a hurry, I said I didn't have ANY
documentation.

What about the printed docs, you say?
  Me:  Do you have the manuals for Turbo C?
 Unc:  Were there any?
  Me:  I'm sure there were.
 Unc:  Sorry, it's been a while since I bought it.  But I must have them,
       I didn't throw anything away.
  Me:  Can I use them?
 Unc:  Sure.  You wanna poke around, see if you can find them?
 
At this I declined.  If you saw my Uncle's house, you would, too.  He's a
pack-rat, and it would take much more time than I have to devote to it. 
 
So, I turn to the great and good comp.lang.c of Internet for wisdom and
guidance.
 
>If you don't find the god-damned help screen helpful, go out and
>purchase the software and read the documentation that comes with it!

I thought I'd better explain myself before some of that wisdom and guidance
called the FBI.
 
It took me 20 lines to explain why I don't HAVE the documentation, 20 lines
of completely wasted bandwidth and reading time to anyone NICE ENOUGH TO
HELP!  I still think "but not the documentation" was, on the whole, better.

>I hope this 'educates' you.
Ditto.

>Judging from your display of common sense,
>it may take a while for this to sink in.

On this one, I'm afraid I can't complain.  It never occurred to me that I'd
be accussed of pirating.  I appologize to anyone who need an appology.  (Those
being the polite, helpful, and scholarly, not the flamers.)
 
I would like to thank those who sent me useful information.  You know who you
are.

To the individual who wrote the above, which was by far the most vicious flame
I received, I can only thank you for doing it privately.  I will reciprocate
by leaving your name off this reply.
 
There, is everyone happy?
 
Steve L Vissage II