Proposing a cIniFile change
#5
I'd say this is convoluted. We need to jump through hoops for the expected behavior.

How about this subtle change:
- GetValue() reads the first value of the specified name
- SetValue() overwrites the first value of the specified name; creates if not found
- EnumValues() reads all the values of the specified name
- AddValue() adds a possibly duplicate name=value pair

This would make all intentions in the code clear - you'd know if the code expects to work with duplicates or not. Also all of this could be exported to plugins and this API is much cleaner, imho.
Reply
Thanks given by:


Messages In This Thread
Proposing a cIniFile change - by xoft - 04-21-2012, 02:30 AM
RE: Proposing a cIniFile change - by FakeTruth - 04-21-2012, 02:33 AM
RE: Proposing a cIniFile change - by xoft - 04-21-2012, 04:19 AM
RE: Proposing a cIniFile change - by FakeTruth - 04-21-2012, 07:13 AM
RE: Proposing a cIniFile change - by xoft - 04-22-2012, 09:52 PM
RE: Proposing a cIniFile change - by FakeTruth - 04-23-2012, 12:12 AM
RE: Proposing a cIniFile change - by xoft - 04-23-2012, 06:41 AM
RE: Proposing a cIniFile change - by FakeTruth - 04-23-2012, 07:24 AM
RE: Proposing a cIniFile change - by xoft - 06-10-2012, 12:33 AM
RE: Proposing a cIniFile change - by xoft - 06-10-2012, 01:53 AM
RE: Proposing a cIniFile change - by FakeTruth - 06-10-2012, 06:43 AM



Users browsing this thread: 4 Guest(s)