From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oren Laadan Subject: Re: Prefix / Naming USERCR API Date: Sat, 10 Apr 2010 09:06:00 -0400 Message-ID: <4BC077B8.6060305@cs.columbia.edu> References: <20100406020221.GA647@us.ibm.com> <1270709399.2602.48.camel@pagloppaglop> <20100410034840.GA11028@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100410034840.GA11028-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Sukadev Bhattiprolu Cc: Containers List-Id: containers.vger.kernel.org Sukadev Bhattiprolu wrote: > | > So, what would be a good prefix ? > | > > | > cr_ > | > cr_checkpoint.h, libcr.a > | > cr_checkpoint() cr_restart() cr_freeze() cr_migrate() > | > struct cr_checkpoint_args, struct cr_restart_args > | > acr_ > | > Only advantage over 'cr_' is lesser likelihood of collision > | > > | > acr_checkpoint.h, libacr.a > | > acr_checkpoint() acr_restart() acr_freeze() acr_migrate() > | > struct acr_checkpoint_args, struct acr_restart_args > | > > | > lxcr_ > | > lxcr_checkpoint.h, liblxcr.a > | > lxcr_checkpoint() lxcr_restart() lxcr_freeze() lxcr_migrate() > | > struct lxcr_checkpoint_args, struct lxcr_restart_args > | > | I do not think lxcr_ prefix is a good choice as lxc is about container > | and could use different libraries for the checkpoint/restart function. > > I was thinking of lx as short for linux, but ok. we can drop lxcr_. > > Any NACKS to 'acr_' ? If not, I will go with it - for now :-) > I vote for 'cr_' to match the terminology we use in the docs and emails ('c/r'). ... and for brevity :p Oren.