Re: [vote] Final API file names and include dir names

2010-02-06 Thread Leif Hedstrom
One more thing I'd like to briefly discuss. After working on the SimpleDBM class, I realized that this could actually be very useful to expose to plugin developers. It simplifies the usage of simple key-val DBs, and provides a unified and installation independent abstraction for the plugin to

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Leif Hedstrom
On 02/04/2010 09:43 PM, Leif Hedstrom wrote: The above would make it pretty darn easy to compile for multiple versions, just change the /active/ symlink accordingly. I should say, it gives several options for building for multiple versions: 1) Change the symlink (in my modified proposal). 2)

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Leif Hedstrom
On 02/04/2010 05:04 PM, John Plevyak wrote: Another question is how do we want to handle versions? Should we have: ats/ats-2.0.h ? gtk uses /usr/include/gtk-2.0 python in /usr/include/python2.5 gcc uses /usr/include/g++/4.1.2 Some folks also have a single .h which pulls in everything:

Re: [vote] Final API file names and include dir names

2010-02-04 Thread John Plevyak
Looking at /usr/include on my Linux system, it seems that the vast majority of directory names are short acronyms. And yes, most have no meaning and are just used to disambiguate otherwise similar names (like prepending X or G before all your public function names). Given that I don't find 1 comp

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Bryan Call
Just to clarify my position: 1. ts is a crappy name for a directory, it has no meaning and it is like naming a variable x or y. I believe that directories, files, variables, functions, etc should have meaningful names. Most people use tab complete or text complete by now or at least they sho

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Leif Hedstrom
On 02/04/2010 12:31 PM, Jason wrote: I'd like to voice a comment, ${prefix}/ts seems somewhat vague unless you were going to rename all the scripts ts. My eyes can read quite clear exactly what this header is even if i had no idea what trafficserver was and just happened to be reading some rand

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Leif Hedstrom
On 02/04/2010 02:35 PM, Bryan Call wrote: There is already code that uses the ts directory for include files (simple google search, there might be others): http://isscvs.cern.ch/cgi-bin/viewcvs-all.cgi/TriDAS/trigger/ts/framework/src/common/CellOpInit.cc?revision=1.35&root=tridas&view=markup

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Bryan Call
There is already code that uses the ts directory for include files (simple google search, there might be others): http://isscvs.cern.ch/cgi-bin/viewcvs-all.cgi/TriDAS/trigger/ts/framework/src/common/CellOpInit.cc?revision=1.35&root=tridas&view=markup [x] ts_api.h [x] ${prefix}/trafficserver -B

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Jason
I'd like to voice a comment, ${prefix}/ts seems somewhat vague unless you were going to rename all the scripts ts. My eyes can read quite clear exactly what this header is even if i had no idea what trafficserver was and just happened to be reading some random piece of code: "#include " Just som

Re: [vote] Final API file names and include dir names

2010-02-04 Thread George Paul
InkApi.h rename: [ ] api.h [X] ts_api.h [ ] sdkapi.h Include directory name - [X] ${prefix}/include/ts [ ] ${prefix}/include/trafficserver -George On 2/3/10 8:08 PM, Leif Hedstrom wrote: > So, I think the discussions have had enough time

Re: [vote] Final API file names and include dir names

2010-02-04 Thread Leif Hedstrom
On 02/03/2010 09:08 PM, Leif Hedstrom wrote: Include directory name - [ ] ${prefix}/ts [ ] ${prefix}/trafficserver I'm an idiot, but I'm hoping everyone realized the above was a typo, the directory names would obviously be one of ${prefix}/include/ts $

Re: [vote] Final API file names and include dir names

2010-02-04 Thread John Plevyak
ncubator.apache.org > Sent: Wed, February 3, 2010 8:08:51 PM > Subject: [vote] Final API file names and include dir names > > So, I think the discussions have had enough time, the consensus is definitely > that we should clean up what we got. As such, we will move both include f

Re: [vote] Final API file names and include dir names

2010-02-03 Thread Leif Hedstrom
My votes are: InkApi.h rename: [x] api.h [ ] ts_api.h [ ] sdkapi.h Include directory name - [x] ${prefix}/ts [ ] ${prefix}/trafficserver -- Leif

Re: [vote] Final API file names and include dir names

2010-02-03 Thread Tin Zaw
, February 3, 2010 8:08:51 PM Subject: [vote] Final API file names and include dir names So, I think the discussions have had enough time, the consensus is definitely that we should clean up what we got. As such, we will move both include files to be in the same directory in SVN, we will rename

[vote] Final API file names and include dir names

2010-02-03 Thread Leif Hedstrom
So, I think the discussions have had enough time, the consensus is definitely that we should clean up what we got. As such, we will move both include files to be in the same directory in SVN, we will rename RemapAPI.h to remap_api.h, and we will install the two header files in a well defined in