RE: help: tips from c++ api writers

Subject: RE: help: tips from c++ api writers
From: "walden miller" <wmiller -at- vidiom -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 5 Apr 2001 13:30:54 -0600

Just a few notes:

> C++, OTOH, stores information about the class in the
> header file (.h) and the implementation (mostly) for the
> class goes in the source file (.c, .cpp, etc. depending
> on the compiler). When you compile c++ code, the
> implementation goes to neverneverland; the header file
> remains in plain text. <TIC> That's why *real* c++
> programmers don't need no stinkin' reference docs!</TIC>
> ;-) They can always browse the header files to see
> what the library includes.

This depends on the programmer and the style used by the company.
I have a number of client programmers that stuff everything into the .cpp
So once its compiled there is no trace of the declarations...

> While Java, with a few exceptions, follows a one-class/
> one-file model, I've seen upwards of 200 classes declared
> in a single header file.

Again, you can declare as many classes as you want in a single .cpp file as
well; it's just not very nice or manageable.

People aren't (typically) forced into bad programming practices, but
writer's have to put up with them:-)



*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available 4/30/01 at or info -at- devahelp -dot- com

Sponsored by DigiPub Solutions Corp, producers of PDF 2001 Conference East,
June 4-6, Baltimore, MD. Now covering Acrobat 5. Early registration deadline
April 27.

You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: Techwriting and Personality
Next by Author: RE: Trivial trivia (not completely off-topic)
Previous by Thread: Re: help: tips from c++ api writers
Next by Thread: Trademark usage guidelines?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads