I like your KISS method. Having 3 or 4 chars plus an underscore before the varname is just to anal for my tastes.
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Albert > Berry > Sent: Sunday, August 10, 2014 1:44 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Clearing variables > > I use a similar system to that Tony uses. I'm lazy so I use a single > character. My system is: > xUserID -- permanent to the entire session. R:Base allows "CLEAR ALL > VAR EXCEPT x%" > pCustID -- variables used in stored procedures. "CLEAR VAR p%" right > before the RETURN > fVendID -- form variables form close eep "f%" > rDate -- Report variables. > vDate -- Made and cleared randomly when needed. > > Albert > > > On 8/10/2014 8:47 AM, Tony IJntema wrote: > > > Tom, > > > > If you use the 64 bits version of Rbase there are pratical no > limitations to the length of the name of a variable. > > What you could consider is to make a distinction between the > various kind of variables. > > > > Example: > > All global variables could start with VG_ or just V_ (V > underscore) > > All local variables could start with VL_ > > Variables which never change in the application could start with > VC_ > > > > In this case the only thing you have to do at the end of each > procedure is using the statement: clear var VL_% > > Then all local variables will be cleared. > > > > I am using this kind of convention for some years now and it > works very fine. > > Never be surprised by an unexpected value of a variable > > It also forces you to think about the usage of the kind of > variables in a procedure. > > The nice thing is also that you can see quickly what kind of > variable you are looking at > > > > Tony > > > > From: [email protected] [mailto:[email protected]] On Behalf Of > Buddy Walker > Sent: zondag 10 augustus 2014 13:00 > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Clearing variables > > > > Tom > > When I used an external form to connect to a database I would > clear all variables when finished. The only exception would be the > variables I need to control the external form. I always tried to clear > variables that I wouldn't need after using the fom_action. > > > > If it is the same session of R:Base and you didn't clear the > variables then they would be defined. The problem I see with that is a > variable may still have a value that you may not be expecting. > > > > Buddy > > > > From: [email protected] [mailto:[email protected]] On Behalf Of > TOM HART > Sent: Saturday, August 09, 2014 10:47 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Clearing variables > > > > I am in the process of using external forms to run my apps, so > that the database will only be connected when a button is pushed. For > years I have been running command files and eeps but never clearing the > variables. Lately I saw some posts that unused variables should be > cleared after being used. So my question is, can I use the 'clear all > var' in say an on close eep and do defined variables specific to each > connection. Example, maybe I am processing a sales order(where I have > used defined variables), then decide to start another sales order(same > variables defined), if I finish one order, exit, and clear all > variables will they still be defined in the open one. > > > > Tom Hart > --- RBASE-L ================================================ TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO ================================================ TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE ================================================ TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. ================================================
