Anonymous user
Talk:Update a configuration file: Difference between revisions
m
→Task spec issues: added a what-if case query.
(→Task spec issues: directive file.) |
m (→Task spec issues: added a what-if case query.) |
||
Line 21:
:: The phrase ''If a configuration option does not exist with the file'' is a bit vague. What does ''<big><big>a</big></big> configuration option'' mean? One (or any) of the aforementioned options mentioned earlier in the Rosetta Code tasks? Explicitly stating which options would be clearer and unambiguous. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 03:00, 12 May 2015 (UTC)
:: What about the case of:
<pre>
; prunes 10
peaches 20
apples none
prunes 48
</pre>
:: and let's say that the PRUNES option setting to be "un-commented" (as per a task requirement). Then, the 2nd PRUNES option setting would be deleted as per a stated rule (as there is now a duplicate PRUNES option). Is this what the author had in mind? -- to invalidate an existing option setting when "un-commenting" an option setting? It almost looks like the task's requirements might possibly require a two-pass solution for the above scenario. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 07:02, 12 May 2015 (UTC)
:: If the author of the task wanted to have duplicate entries (as well as spurious duplicate semicolons) removed, there should be some examples of each in the input file (plus the addition of same wouldn't change the output file, even at this late date). -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 03:00, 12 May 2015 (UTC)
| |||