linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Harrison <matth@3d-computers.co.uk>
To: linux-c-programming@vger.kernel.org
Subject: named structure members
Date: Thu, 11 Sep 2003 12:07:42 +0100	[thread overview]
Message-ID: <20030911110742.GD6863@3d-computers.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

hi,
  another one for you gurus, i haven't found anything on this myself
as i don't really know what to call it where a search engine is
concerned.

i have the following code.

<snip>
for(i = 0; i < n_values; ++i)
        {
                strcpy(keyword, good_values[i]);

                switch (read_config_var(values_file, keyword, value))
                {
                        case 0:
                                strcpy(config.?, value);
                                break;
                        case -1:
                                printf("\nFile Error for [%s] \n", values_file);
                                break;
                        case -2:
                                printf("\nBad User Parm for [%s] \n", keyword);
                                break;
                        default:
                                printf("\nUnknown Error Occurred \n");
                                break;
                }
        }
</snip>

what i'm doing is stepping thru an array of different config options
calling the read_config_var on each one and checking the output.
if the output is good then i want to store the value in a member of
a structure. for example i want the config options to be stored like
this:

config.db_host = 'maiden.genestate.com'
config.db_user = 'root'

you get the idea. my question is how do i dynamically assign a name
to a structure member. I have good_values[i] which contains the
current config directive but if you look at line 8 of the example,
you can see the problem, how do i say config.good_values[i], when
good_values[i] is not itself a member.

sorry for not being able to explain this very well but you can see
what i mean.

thanks in advance

-- 
Mat Harrison
Technical Developer
3d Computer Systems Ltd.
matth@3d-computers.co.uk

[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]

             reply	other threads:[~2003-09-11 11:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 11:07 Matthew Harrison [this message]
2003-09-11 11:50 ` named structure members Jeff Woods
2003-09-11 14:03 ` Mariano Moreyra
2003-09-11 14:26   ` Matthew Harrison
2003-09-11 14:41     ` Mariano Moreyra
2003-09-11 15:28       ` Matthew Harrison
2003-09-11 15:35         ` Mariano Moreyra
2003-09-11 15:42           ` Matthew Harrison
2003-09-11 15:50     ` Glynn Clements
2003-09-11 16:52       ` Jan-Benedict Glaw
2003-09-11 17:13         ` Matthew Harrison
2003-09-12 13:22           ` Mariano Moreyra
2003-09-12 13:47             ` Matthew Harrison
2003-09-12 13:52               ` Mariano Moreyra
2003-09-12 14:33                 ` Matthew Harrison

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=20030911110742.GD6863@3d-computers.co.uk \
    --to=matth@3d-computers.co.uk \
    --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).