Mailinglist Archive: opensuse-programming (96 mails)

< Previous Next >
Header Files, CommonC++ && All that?
  • From: "Steven T. Hatton" <hattons@xxxxxxxxxxxxxxxxxx>
  • Date: Tue, 25 Mar 2003 10:45:05 -0500
  • Message-id: <200303251045.05749.hattons@xxxxxxxxxxxxxxxxxx>
I want to use the class described on the page found here on my SuSE 8.1. (It
requiers the CommonC++ documentation to be installed.)
file:///usr/share/doc/packages/CommonC++-doc/html/classost_1_1_string_tokenizer.html#_details

How would one typically (correctly) include such a library in his code? If I
follow K&R 2nd. Ed., they put the #includes for libraries in any .c file that
relies on them. Is that technically necessarily? From my experimentation,
id doesn't /seem/ to be necessary. All that is required to get the code to
run is that the one of the header files referenced in the .c includes the
particular library.

But 'technically' correct, and stylistically correct are not the same thing.
What is the prefered /style/?

Is this CommonC++ library really common? If I put it in my code and
distribute it, will a bunch of people curse me? Is it the best bag of trick
to draw from for general functionality such as string tokenization. I'm
writing for a QT/KDE environment.

STH

< Previous Next >