Professional Web Applications Themes

Ideas for a modular config file? - UNIX Programming

Hi folk, Right now I have a project that has a "bind-style" config file that is pd with the aid of flex and bison. It looks a bit like this: foo { some_key = "value"; another_key = 42; }; bar { you = "get the idea I suspect"; }; In my code, I have structures that would be like this: struct foo { char *some_key; int another_key; } foosection; struct bar { char *you; } bction; Then the pr produced by bison reads the config file and fills in each section's structure with the relevant values. All well and good, ...

  1. #1

    Default Ideas for a modular config file?

    Hi folk,

    Right now I have a project that has a "bind-style" config file that is
    pd with the aid of flex and bison. It looks a bit like this:

    foo {
    some_key = "value";
    another_key = 42;
    };

    bar {
    you = "get the idea I suspect";
    };

    In my code, I have structures that would be like this:

    struct foo {
    char *some_key;
    int another_key;
    } foosection;

    struct bar {
    char *you;
    } bction;

    Then the pr produced by bison reads the config file and fills in each
    section's structure with the relevant values.



    All well and good, but now I come to a stage where I want to add module
    functionality to this software, and some of the modules I wish to write may
    extend the config file syntax.

    I'm very new to bison (yacc) and I don't really understand how I might
    achieve this, since the syntax of my config file seems to need to be
    defined at compile-time whereas modules are obviously a run-time thing.

    Might anyone have any tips?
    Andy Smith Guest

  2. #2

    Default Re: Ideas for a modular config file?

    Andy Smith <andy-newsstrugglers.net> writes:
    > Right now I have a project that has a "bind-style" config file that is
    > pd with the aid of flex and bison. It looks a bit like this:
    >
    > Then the pr produced by bison reads the config file and fills in each
    > section's structure with the relevant values.
    >
    > All well and good, but now I come to a stage where I want to add module
    > functionality to this software, and some of the modules I wish to write may
    > extend the config file syntax.
    >
    > I'm very new to bison (yacc) and I don't really understand how I might
    > achieve this, since the syntax of my config file seems to need to be
    > defined at compile-time whereas modules are obviously a run-time thing.
    >
    > Might anyone have any tips?
    Maybe libtc can be of some use. It has a config file pr with a
    similar syntax. The pr will accept any names of keys and reads
    the entire file into memory. Then you use some functions to extract
    the information you want. The drawback is that you won't catch
    spelling errors and the like.

    [url]http://libtc.sf.net[/url]

    --
    Måns Rullgård
    [email]mruusers.sf.net[/email]
    Måns Rullgård Guest

  3. #3

    Default Re: Ideas for a modular config file?

    Hi,

    Maybe XML is an option


    "Andy Smith" <andy-newsstrugglers.net> schreef in bericht
    news:HLvMa.830$0F.6251545news-text.cableinet.net...
    > Hi folk,
    >
    > Right now I have a project that has a "bind-style" config file that is
    > pd with the aid of flex and bison. It looks a bit like this:
    >
    > foo {
    > some_key = "value";
    > another_key = 42;
    > };
    >
    > bar {
    > you = "get the idea I suspect";
    > };
    >
    > In my code, I have structures that would be like this:
    >
    > struct foo {
    > char *some_key;
    > int another_key;
    > } foosection;
    >
    > struct bar {
    > char *you;
    > } bction;
    >
    > Then the pr produced by bison reads the config file and fills in each
    > section's structure with the relevant values.
    >
    >
    >
    > All well and good, but now I come to a stage where I want to add module
    > functionality to this software, and some of the modules I wish to write
    may
    > extend the config file syntax.
    >
    > I'm very new to bison (yacc) and I don't really understand how I might
    > achieve this, since the syntax of my config file seems to need to be
    > defined at compile-time whereas modules are obviously a run-time thing.
    >
    > Might anyone have any tips?

    Johan den Boer Guest

Similar Threads

  1. Replies: 3
    Last Post: June 1st, 02:49 AM
  2. Replies: 6
    Last Post: October 31st, 02:34 PM
  3. Modular Photoshop?
    By Leen Koper in forum Adobe Photoshop Elements
    Replies: 4
    Last Post: September 23rd, 11:58 PM
  4. File plays offline but only one button works online... Any ideas?
    By big vern webforumsuser@macromedia.com in forum Macromedia Flash Sitedesign
    Replies: 1
    Last Post: August 15th, 05:27 PM
  5. Modular design using ASP
    By Paul Baker in forum ASP
    Replies: 5
    Last Post: August 8th, 09:53 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139