Good information, all. Everyone has - and can articulate - their own unique approach; a clear example of having it your way in R:Base, it appears.
Thank you! Bruce Chitiea SafeSectors, Inc. > -------- Original Message -------- > Subject: [RBASE-L] - RE: Object Naming Conventions > From: "A.G. IJntema" <[email protected]> > Date: Tue, February 21, 2012 1:16 am > To: [email protected] (RBASE-L Mailing List) > > > Hi Bruce, > > I apply quite strict naming conventions. > It really helps when debugging > Using 64 bits version of R:base there are no length limitations anymore. > > For tables I am using a three or four letter abbreviation followed by an > underscore, which is created from the full name. > I'll take the first letter of the first syllable, the first letter of the > last syllable and the last letter of the last syllable > ( In practice this convention creates a quite unique abbreviation (at least > in Dutch, which I am.) > > For instance: > OTL_Orderdetail > CCT_Client ( there is just one syllable, so the first is also the last > syllable in this word) > > All columnnames of that particular table start with this abbreviation > For instance: > CCT_ID (always the primary key) > CCT_Name > > In this way you will see in a glance to which table a column belongs > Also a foreign key is recognized easily. > > Variables start normally with the letter V_ (V underscore) > Like: > V_CCT_ID > V_CCT_Name > > This is more or less the same naming convention R:base uses. I have added the > underscore, because of the readability (because the length is not really > important anymore) > > I have added some other types of variables, like > VL_ -> local variables. This kind of variables are cleared at the end of a > procedure. It can be done simply using the statement: CLEAR VAR VL_* > Using this kind of variables makes it easier to do some housekeeping and it > also enforces you to think about the nature of the used variable in a > procedure. > > VC_ -> Variables which effectively contains a constant value throughout the > whole session and mostly defined and filled when the application is started. > > Temp tables start with T_ like T_CCT_Client > > And so on. > > Hope this might help. > > Tony IJntema > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Bruce Chitiea > Sent: maandag 20 februari 2012 23:32 > To: RBASE-L Mailing List > Subject: [RBASE-L] - Object Naming Conventions > > All: > > Any feelings one way or the other about 'prefixed' object naming conventions? > > ... such as: > > tb_<tablename> > tt_<temptablename> > vw_<viewname> > fm_<formname> > rp_<reportname> > > Over time, is this helpful in building/maintaining code, or just extra typing? > > Thanks, > > Bruce Chitiea > SafeSectors, Inc.
