Not to kick off a naming/code convention war, but it would be so much better to have just one convention for a project. The code can freely call platform specific routines that don't adhere to the convention (for e.g. Windows library calls), and that is fine. In fact, it makes it easy to identify what is an "implmented functionality", and what is a "native platform provided functionality".
-- Saurabh > -----Original Message----- > From: Alin Serdean [mailto:aserd...@cloudbasesolutions.com] > Sent: Wednesday, August 06, 2014 12:54 PM > To: Nithin Raju > Cc: Saurabh Shah; Samuel Ghinet; dev@openvswitch.org > Subject: RE: [ovs-dev] [PATCH 02/15] datapath-windows: Move and Rename > files > > I fully understand Nithin, maybe it is just me :). > > -----Mesaj original----- > De la: Nithin Raju [mailto:nit...@vmware.com] > Trimis: Wednesday, August 6, 2014 10:46 PM > Către: Alin Serdean > Cc: Saurabh Shah; Samuel Ghinet; dev@openvswitch.org > Subiect: Re: [ovs-dev] [PATCH 02/15] datapath-windows: Move and Rename > files > > On Aug 6, 2014, at 12:36 PM, Alin Serdean > <aserd...@cloudbasesolutions.com> > wrote: > > > One another thing that comes to mind would be to have filenames in > lowercase, but maybe that is just me. > > Alin, > Windows seems to encourage CamelCasing. Hence we named the files as > such. > > -- Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev