Groups > comp.os.linux.development.apps > #314

Re: file parsing

From	Rainer Weikusat <rweikusat@mssgmbh.com>
Newsgroups	comp.os.linux.development.apps
Subject	Re: file parsing
Date	2011-12-13 22:56 +0000
Message-ID	<87r508ulm1.fsf@sapphire.mobileactivedefense.com> (permalink)
References	<jc8h3u$98o$1@dont-email.me> <8762hkyu5j.fsf@araminta.anjou.terraraq.org.uk> <jc8keo$t5d$1@dont-email.me>

Show all headers | View raw

Bill M <wpmccormick@just_about_everywhere.com> writes:
> On 12/13/2011 4:38 PM, Richard Kettlewell wrote:

[...]

>> XML is a poor choice for config files,

[...]

> I found this for parsing ini config files:
>
> http://code.google.com/p/inih/
>
> Looks like exactly what I'm looking for.

If your requirements are simple enough, consider not parsing a config
file: Anything which can be expressed as otherwise unstructured list
of name=value pairs can be put into a file the shell can source and
then start another program with a set of command-line arguments
derived from the parameters.

Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

file parsing Bill M <wpmccormick@just_about_everywhere.com> - 2011-12-13 15:46 -0600
  Re: file parsing Richard Kettlewell <rjk@greenend.org.uk> - 2011-12-13 22:38 +0000
    Re: file parsing Bill M <wpmccormick@just_about_everywhere.com> - 2011-12-13 16:43 -0600
      Re: file parsing Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-12-13 22:56 +0000
        Re: file parsing David Brown <david@westcontrol.removethisbit.com> - 2011-12-14 08:48 +0100
  Re: file parsing Jasen Betts <jasen@xnet.co.nz> - 2011-12-18 09:57 +0000

csiph-web