----- Original Message -----
> Hi all,
>
> I'd like to propose that we start using ats_ as a prefix for new APIs
> (and rewrites etc.) in the internal code. Long term, we probably

Can you please break down for us what exactly internal code is.

> should
> migrate existing ink_ prefixes to ats_, and perhaps also consider
> using
> C++ name spaces.  My rationale for using "ats" instead "ts" in the

So this is - in the long term, going to be more than a

  sed -i 's/\bink_/ats_/g' **/*.cc **/*.[ch]

> internal (core) code is to make it easily distinguishable from the
> public APIs (which are all prefix e.g. TS or ts). This is very useful
> when grepping through the code IMO.

Just have to teach people *how* to grep ;)

igalic@tynix ~/src/asf/trafficserver (svn)-[trunk:1162727] % ack-grep '\bink_'  
| wc -l
8333
igalic@tynix ~/src/asf/trafficserver (svn)-[trunk:1162727] % ack-grep 'ink_'  | 
wc -l
8540
igalic@tynix ~/src/asf/trafficserver (svn)-[trunk:1162727] %

> Cheers,
>
> -- Leif


So long,

i

--
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

Reply via email to