We code to our IDE. Since we use toad for our PL-SQL development we always format our code with that. But we're a pretty loose division generally. --Ben. >>> ra3masis@xxxxxxxxx 8/25/2005 12:56:23 PM >>> 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 ------------------------------------------------------------------------------ This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed. ------------------------------------------------------------------------------