Re: Coding Standards - are there any ?

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 48545
interpreted = N
texte = For whatever it's worth, I am an admittedly non-advanced programmer and I like to write my WebDNA code as literal and deliberate as possible, so that when I read the code it almost sounds like plain english to me:Example:-----------------------------------Database Header ----> UNIQUEEMAILVERIFIED-----------------------------------[search db=email_addresses.db&eqVERIFIED=Y] [founditems] [sendmail to=[EMAIL]&from=me@xxx.com&subject=Hello] This is the body of the email. [/sendmail] [/founditems][/search]-----------------------------------I don't know if that was totally helpful, but I think you get the idea. I prefer to name things according to what they are and what their function is. Kind of simplistic, but it keeps me sane. I've noticed that some folks like to prefix their form-variables with underscores (___FORM-VARIABLE-1), and things of that nature. I can see where it would be useful, but for me, it's a chore enough just to build some of this (to me) damn complex stuff, and the last thing I need is another sub-task to potentially confuse me.That said, to each their own, right? Ok back to work for me. Hope this helped.-Dan------------------------------------------------------------http://www.StrongGraphicDesign.com(208) 319-0137 | Toll-free p/f 877-561-1656------------------------------------------------------------On Mon, 10 Mar 2003 16:48:51 -0000 Tom Duke wrote:>Hi all,>>I keep changing my database/field naming conventions to ones that seem more logical. Before I do >this again does anyone have a good set of coding standards/recommendations.>>So far I have used conventions like:->> F_FIELDNAME> V_VARIABLENAME> R_RECORDID>>or>> fFIELDNAME> vVARIABLENAME> rRECORDID>>etc.>>Thanks>- Tom>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Coding Standards - are there any ? (Alan White 2003)
Re: Coding Standards - are there any ? (Terry Wilson 2003)
Re: Coding Standards - are there any ? (Tom Duke 2003)
Re: Coding Standards - are there any ? (Charles Kline 2003)
Re: Coding Standards - are there any ? (Howard Wolosky 2003)
Re: Coding Standards - are there any ? (Kimberly D. Walls 2003)
Re: Coding Standards - are there any ? (Dan Strong 2003)
Re: Coding Standards - are there any ? (John Peacock 2003)
Coding Standards - are there any ? (Tom Duke 2003)

For whatever it's worth, I am an admittedly non-advanced programmer and I like to write my WebDNA code as literal and deliberate as possible, so that when I read the code it almost sounds like plain english to me:Example:-----------------------------------Database Header ----> UNIQUEEMAILVERIFIED-----------------------------------[search db=email_addresses.db&eqVERIFIED=Y] [founditems] [sendmail to=[EMAIL]&from=me@xxx.com&subject=Hello] This is the body of the email. [/sendmail] [/founditems][/search]-----------------------------------I don't know if that was totally helpful, but I think you get the idea. I prefer to name things according to what they are and what their function is. Kind of simplistic, but it keeps me sane. I've noticed that some folks like to prefix their form-variables with underscores (___FORM-VARIABLE-1), and things of that nature. I can see where it would be useful, but for me, it's a chore enough just to build some of this (to me) damn complex stuff, and the last thing I need is another sub-task to potentially confuse me.That said, to each their own, right? Ok back to work for me. Hope this helped.-Dan------------------------------------------------------------http://www.StrongGraphicDesign.com(208) 319-0137 | Toll-free p/f 877-561-1656------------------------------------------------------------On Mon, 10 Mar 2003 16:48:51 -0000 Tom Duke wrote:>Hi all,>>I keep changing my database/field naming conventions to ones that seem more logical. Before I do >this again does anyone have a good set of coding standards/recommendations.>>So far I have used conventions like:->> F_FIELDNAME> V_VARIABLENAME> R_RECORDID>>or>> fFIELDNAME> vVARIABLENAME> rRECORDID>>etc.>>Thanks>- Tom>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Dan Strong

DOWNLOAD WEBDNA NOW!

Re: Coding Standards - are there any ?

2003

Top Articles:

Related Readings: