Talk:Update a configuration file

Task spec issues

This task spec seems needlessly complex. For example "In commenting out an option, any duplicates should also become commented." does this mean that changes should be made by commenting out the old option instance and adding a new line? If not, how can we satisfy this requirement in the task implementation? --Rdm 11:33, 20 May 2011 (UTC)

He's trying to get us to duplicate the (over-complex IMO) functionality that he put into his implementation of this task. –Donal Fellows 13:38, 20 May 2011 (UTC)

Ok, I have reworded that so that duplicate entries can simply be removed.

--User:Markhobley 15:46, 20 May 2011 (UTC)

It's still a requirement beyond the scope of the task -- hypothetically speaking, someone could implement this functionality using assert("FIXME") and documentation that the person using the program should manually edit the binary image using a debugger, and no user interaction would be required for the task. And, it's not the only such requirement, either. --Rdm 16:01, 20 May 2011 (UTC)

I'm not sure what that means. --Markhobley 22:44, 3 June 2011 (UTC)

All that stuff about duplicate entries and duplicate semicolons is B.S. If the update program doesn't produce such crap, it shouldn't have to deal with it. Either you use the program for updating the file, or you're on your own.24.85.131.247 06:26, 22 October 2011 (UTC)