Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

Re: file parsing

Show all headers | View raw

On 13/12/2011 23:56, Rainer Weikusat wrote:
> 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.

It also depends on your choice of language.  For example, if the program 
is in Python or Perl, you could have your settings in a Python or Perl 
program - use the language itself as the parser.  Obviously you'll want 
to be careful about security in such cases.

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