On Oct 5, 2009, at 10:34 AM, Brice Goglin wrote:
> I haven't had time to actually fully implement this yet, but my last
> plan was opaque pointer + functions such as:
> hwloc_cpuset_t hwloc_cpuset_alloc(void);
> void hwloc_cpuset_destroy(hwloc_cpuset_t cpuset);
Minor quibble: it might be good to have nice "opposites" in the verbs
-- alloc and free, create and destroy, etc.
> hwloc_cpuset_t hwloc_cpuset_copy(hwloc_cpuset_t cpuset);
> typedef struct hwloc_cpuset_s * hwloc_cpuset_t;
I like having the concept of a fully opaque pointer such that users
will be compelled to use the alloc/free functions.