Will this problem (leading comments preventing correct compilation of packages) be fixed in the next release? And if so, any idea on how far out this release will be (days/weeks/months)?
I just noticed an interesting wrinkle: I compiled a package body with an error, so the package body got a little red X in the browser. When I corrected the error and compiled the package body with excess remarks, I got the "Compiled Successfully" message but the red X didn't go away. Then I deleted the remarks and recompiled; this time the red X went away.
- I compiled a package body with an error so the icon got a little red X in the browser.
- I corrected the error and recompiled, but the code had "excess" comments at the beginning. Although I got the "compiled successfully" message, the red X did not go away.
- I deleted the comments and recompiled. This time the red X went away when I got the "compiled successfully" message.
I think it actually compiles because it takes a while. Also, if I compile with all the remarks AND an error, it for sure compiles because it takes some time about it and it says "Compiled with errors." It won't tell you what the errors are, however.
Further experimentation shows that it fails to "uncheck" the body icon only when there is a keyword early in the comments. When I change the word "package" to "pachage" in the second line of my comments and compile a clean package body, the red check comes off.