From: Malitsky, N. D <mal...@bn...> - 2010-08-09 15:30:07
|
dbCPP aims to provide a common framework for adapting both epics 3 and new structured records. Actually, I prefer 'old' names (like db) to preserve this transition. In any case, changing the repository name is easy. The immediate suggestion (from Michael Davidsaver) is to drop 'org' in the namespace, e.g. epics::db rather than org::epics::db. I like it. It is consistent with Google's style as well. -----Original Message----- From: Ralph Lange [mailto:Ral...@be...] Sent: Monday, August 09, 2010 10:56 AM To: epi...@li... Subject: Re: update on the mercurial repository On 09.08.2010 10:27, Malitsky, Nikolay D wrote: > OK. According to the suggested naming convention, I will rename db4_cpp > with dbCPP. > Nikolay If that package is the interface to the existing EPICS V3 database, maybe show that by calling it "db3" instead of just "db"? If it is the javaIOC implementation in C++, we were thinking of renaming the javaIOC to "pvEngine", so that the C++ version would be "pvEngineCPP" (following the convention used for the other names). Ralph ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev |