why not default all named objects and if there's anonymous then prefix that with anon: eg shmem (shared mem) mfile (mem mapped) gamem (global/heap alloc mem) uamem (user alloc mem) and if these apply: anon_shmem anon_mfile etc.. ----- Original Message ----- From: "Kim Barrett" <kab@irobot.com> To: <boost@lists.boost.org> Sent: Tuesday, February 28, 2006 8:08 AM Subject: Re: [boost] [interprocess, aka shmem] Some proposals for open issues from the review
named_shared_memory named_mapped_file named_heap_memory etc.
Some users have suggested more descriptive names:
objects_in_shared_memory objects_in_mapped_file objects_in_heap_memory objects_in_user_memory
A bit long but I think the class expresses very clearly its use. We can make it shorter with "objects_in_shmem"/"objects_in_mfile", but is not very pronounceable. This name issue is harder than the review! Comments?
Some more alternatives in the naming scheme race:
- xxx_with_allocation, i.e. shared_memory_with_allocation, heap_with_allocation
- managed_xxx, i.e. managed_shared_memory, managed_heap
Send instant messages to your online friends http://au.messenger.yahoo.com