I'd have to agree with the people who've suggested using XML. Using XML simplifies learning the syntax and makes it easier to write tools for editing the config files that won't conflict with hand-editing the config files. If some people want to dynamiclly generate portions of the config file (rather than all at once prior to reading the file) then I'd go with some sort of tag that specifies the path to that program. Then if I want to write a section in Java, one in PHP, one in Python, one in TCL, and one in a shell script I can without messing up my nice-neat XML config file. Possibly could even allow inline code in cases where we're using a scripting language and not calling a binary.
- Re: plex86.conf script file ideas Andrew Kenneth Milton
- Re: plex86.conf script file ideas Cedric Adjih
- Re: plex86.conf script file ideas Michael Zedeler
- Re: plex86.conf script file ideas Ramon van Handel
- Re: plex86.conf script file ideas Kevin Lawton
- RE: plex86.conf script file ideas Drew Northup
- Re: plex86.conf script file ideas Kevin Lawton
- RE: plex86.conf script file ideas Drew Northup
- Re: plex86.conf script file ideas Ramon van Handel
- Re: plex86.conf script file ideas Wouter Coene
- Re: plex86.conf script file ideas Mailing List Mailbox
- Re: plex86.conf script file ideas Faraj Meir
- Re: plex86.conf script file ideas Chris Emerson
- Re: plex86.conf script file ideas Perry E. Metzger
- RE: plex86.conf script file ideas Drew Northup
