Changing this will remove any weird issues normal KV's can have with group
names.
Note that this change will require significant changes to how UMC processes the
mapcycle. Instead of passing the KV handle to all functions dealing with a
mapcycle, instead we will have to pass around some other structure to represent
them.
Possibilities:
1) Tries (of Tries)
2) A KV which is gaurenteed to have the correct information (all fields which may be ambiguous when parsed by the KV parser will be stored in a non-ambiguous way [i.e. as Values rather than Sections]).
Original issue reported on code.google.com by Steell1...@gmail.com on 3 Mar 2012 at 6:12
Original issue reported on code.google.com by
Steell1...@gmail.com
on 3 Mar 2012 at 6:12