e do not call the list a list? > > The structure is not generic list to store any generic data inside, it just > stores name=value pairs, therefore I think the name 'list' is inappropriate. > In addition, I am tempted to use the structure also for parameters of an > controller in struct cgroup_controller.control_value (to get rid of > FILENAME_MAX and CG_VALUE_MAX arrays), but it requires rewrite of the > structure from list to dynamic array (which is simple, but would require > rename of the structure from 'list' to 'array' or 'vector'). > > Therefore I suggest name which does not say *how it is stored*, but *what is > stored*. Ok, 'dictionary' may be misleading. Any other suggestions? >
So then why not a store? :-) Dhaval ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Libcg-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libcg-devel
