Everyone here pretty much as their own style. I use SQL*Navigator and have configured the PL/SQL formatter to get *close* to my personal style. That way, whenever debugging someone else's code, a one click format get it readable for me. If the developer no longer works here, I leave it that way. Some of my personal preferences: "v_*" for local variables "p_*" for all parameters align all "in", "out", & datatypes vertically two space indent (no tabs!) all code modifications annotated with M#001 ... M#nnn and documented in the source file header. A quick search finds all related changes. Thanks, Jon Knight -----Original Message----- From: oradev-bounce@xxxxxxxxxxxxx [mailto:oradev-bounce@xxxxxxxxxxxxx] On Behalf Of Eddie Awad Sent: Jueves, 25 de Agosto de 2005 01:56 p.m. To: oradev@xxxxxxxxxxxxx Subject: Coding Standards, Who Cares. Hi all, to kick off this list, I have always wanted to know if anyone follows any PL/SQL coding guidelines. I know I follow some naming conventions myself, like for example all variables end with a "_v", all input arguments end with a "_in", and output with an "_out". I also avoid declaring explicit cursors unless I have to, and always create packages that encapsulate my procedures and functions. Now, this all may be good if you are the only programmer in the company, but in my opinion, is not sufficient if you are part of a team. See, unless *all* team members follow the *same* coding standard, there is no standard in coding. Where I work, everyone has his/her own coding style. So, if I want to debug one of my colleague's code, I have to spend this extra time and effort to get into his/her coding style. Is this the case where you work? or, nowadays, nobody cares how developers write code as long as it works! What do you think? -- Eddie Awad. http://awads.net/ //www.freelists.org/webpage/oradev //www.freelists.org/webpage/oradev