Mike,

I said it's a personal style issue. Mostly because I also use several other languages than Xbase and NO other language works like Xbase does in this regard. I try my best to keep things the same to reduce the amount of mental translation I have to do.

And no, I don't do procedure main because you'd have to call it to get your program to run *g*. This "rule" for me is only for UDFs stored in their own file.

I no longer use huge procedure files at all, the only ones I did use were the ones for FoxExpress. I believe in small, easily reuseable component packages. And for me that package is a single udf in it's own .prg file. And FWIW I only have about 30 such UDFs across the several projects I'm working on right now.

>So the main .prg for your systems start with the line PROCEDURE MAIN? Tell you what, if you want clean code put a comment in. There's no benefit to putting in an extra line of non-executing code, so you're wasting execution time and you're taking longer to write your code (bug or no bug even if its just a single line, there can be typos, more debugging yech!). We're supposed to put comments in anyways, so why add such an extra line? Further, if you already started with separate prgs, you can better control what routines go into an app/exe. And, you wouldn't ever have to copy and paste subroutines out of the enormous procedure library. Changing an individual prg is faster than finding an individual subroutine in a huge library file and recompiling the entire library file.
>
>Since the bug has existed for so long, are you suggesting that you've been putting the extraneous procedure line despite knowing there was a bug? The logic of this escapes me.
>
>This sounds more like a coding convention and since people treat that like religion, we'll just have to end this thread here right <g>?