Please read the abstract given below and also:
ftp://rtfm.mit.edu/pub/usenet/news.answers/news-newusers-intro
[QUOTE]
If you DO decide to ask a question in news.newusers.questions...
If, after checking the postings in news.announce.newusers to see if
your question is answered there, and after looking to see if there is
a more appropriate group in which to post it, and after trying to get
help locally, you still think your question belongs in
news.newusers.questions, then go right ahead and post it.
However, you should keep in mind when preparing your question that
the people who will be reading it and trying to help you are not
mind-readers. We don't know what your site is like. There are
thousands of sites on the USENET, and they're all just a little bit
different, so the more details you can provide when asking your
question, the more likely it is that people will be able to help you.
Try to provide the following information when posting a question.
If you don't know the answers to some of these questions, then try to
find them out from someone at your site and save them so that you can
use them when posting questions in the future:
1. What kind of machine are you working on? For example: Macintosh,
VAX, DECstation, IBM PC, PC compatible (which one), Cray, RS/6000.
2. What operating system is it running? For example: MacOS, MS-DOS,
UNIX, VM/CMS, VMS.
3. What version of the operating system? For example: MacOS 7.0,
Ultrix 4.2 UNIX, BSD 4.3, etc.
4. What news reader (or whatever program you are having trouble with)
are you using? What command do you type to start up whatever
program is giving you trouble?
5. What version of the program is it?
6. If you are trying to interpret some sort of error, what exactly did
you type to provoke the error, what was the exact error, and how is
the actual error different from what you expected to happen? For
example, if you're trying to figure out why a mail message bounced,
what address did you send the mail to, and what error message came
back in the bounced message?
7. What have you done to try to find the answer to your question
before posting? If you've tried different possible answers
already, exactly what have you tried, and what was the result?
8. If you have checked the documentation and cannot understand the
answer it gives to your question, then what exactly about the
answer it gives don't you understand? If there is documentation
available and you haven't checked it, why not?
If you're not sure whether a particular piece of information will be
helpful, include it. It can't hurt to provide extra information
(unless, of course, that information takes up several hundred lines of
text :-), and it may just be the key to the solution of your problem.
[QUOTE]
> Hi,
> Does anyone has some good links for handling some kind
> of configuration file for my programs in c or c++
> Thx in advance !
> __________________________________________________________
> Alcatel Bell Space N.V.
> Berkenrodelei 33, phone : +32 (0)3 829 5658
> B-2660 Hoboken, Belgium. fax : +32 (0)3 829 5763
> --