linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel" <uval@rz.uni-karlsruhe.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: global parameters
Date: Fri, 10 May 2002 11:05:01 +0200	[thread overview]
Message-ID: <001101c1f801$c662e430$544615ac@stud.unikarlsruhe.de> (raw)
In-Reply-To: 463100409.20020419114801@com2com.ru


----- Original Message -----
From: "Eugene Vigovskiy" <vigov@com2com.ru>
Newsgroups: ka.lists.linux.c.programming
Sent: Friday, April 19, 2002 9:48 AM
Subject: global parameters


>   Hello All.
>
>   I'd like to ask one question.
>
>   I've got a programm, and i'd like to read configuration from file.
>   I need in some data structure for it.
>
>   What is the best way to do it?
>
>   I see at least two ways.
>
>   The first is allocate a structure like this
>   struct somestruct {
>          param1;
>          param2;
>          .
>          .
>          paramn;
>   }
>   and create func what will fill and return pointer to it,  that I can use
in any place.
>
>   The Second way is to
>
>   allocate some global variables and make them available through
>   "extern" in other modules.
>   Can anybody point me at advantages and disadvantages of this
>   methods.
>
>
> Eugene Vigovskiy
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>
> --------------------------------------------------------------------------
-----
>    Achtung: diese Newsgruppe ist eine unidirektional gegatete
Mailingliste.
>      Antworten nur per Mail an die im Reply-To-Header angegebene Adresse.
>                    Fragen zum Gateway -> newsmaster@inka.de.
> --------------------------------------------------------------------------
-----

I think the first one is better.
 (If you want to develope this program, you only let these modules see
the declarations that realy need them)
If it going to be small (~200 Lines) then it doesn't matter which one you
use.


      reply	other threads:[~2002-05-10  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19  7:48 global parameters Eugene Vigovskiy
2002-05-10  9:05 ` Daniel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001101c1f801$c662e430$544615ac@stud.unikarlsruhe.de' \
    --to=uval@rz.uni-karlsruhe.de \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).