Anonymous user
Talk:Read a configuration file: Difference between revisions
Which part of the format is not clear from the example?
(Which part of the format is not clear from the example?) |
|||
Line 48:
: I take it you're not dealing with configuration parameters with commas in? (So far as I can see, they're always handled as sequence separators. Significant leading and trailing space would be another issue.) –[[User:Dkf|Donal Fellows]] 17:18, 24 April 2011 (UTC)
----
Commas are used to separate parameters. In implementations that I have written, the configuration parser passed the parameters to a separate parser, which handles the comma and validation of the parameters. The job of the configuration reader was to read the file, and feed the appropriate parameters to the appropriate variables.
[[User:Markhobley|Markhobley]] 19:11, 24 April 2011 (UTC)
* The authors reason for why he calls it a standard - being created in 1991, is not enough to call it a standard.
* Doing what the source of the original implementation does is not enough to describe the format for other implementations.
The good thing about standards is that we have so many to choose from :-)
We really need a succinct description of the format to get this page moving, or swap to a similar but better documented format. --[[User:Paddy3118|Paddy3118]] 18:07, 24 April 2011 (UTC)
There is a sample file on the task description. Which part of the format is not clear from the example?
We can always create new tasks for other formats of course.
[[User:Markhobley|Markhobley]] 19:11, 24 April 2011 (UTC)
| |||