I disagree. By removing that line all you did was remove a bunch of characters out of the remarks. If you remove that line but substitute the same number of characters for the stuff you removed, the problems still exist.

I'm still convinced that the error occurs when you exceed some magic number of characters in remarks preceding the actual code. Convince me otherwise.

I tested again, and it is indeed a little bit more complicated. Any object type name in the header will cause this error. In this case the following 2 lines:

REM package body create for comp_err - description

REM 08/06/02 Jeff Moritze v27, added procedure for closing cursors.

I'm not sure why I didn't run into this yesterday, and perhaps you can confirm this.

Like I said, we'll fix it. I will send you this fix as soon as it's implemented.

Are you sure you carefully replaced each character you removed from the remarks with another character? You may replace it with any character you want.

Please be sure you understand my premise: The code I sent has one more character in the pre-code remarks than the "magic number" that causes failure. If you want, I will write some code to count those characters and find the number.

Remove one or more characters from the remarks in the code I sent and both problems go away. Add the character back in and the problems reappear. It doesn't matter a bit which character(s) you remove. If you are simply removing the characters "package body" or "procedure" without replacing them, then you have removed "one or more characters". Unless you have replaced characters removed with an equal number of characters and found that the code I sent works, you have not tested my premise.

Now I have to apologize...sort of:

You are right in that if I substitute any character in the words "procedure" and "package" so they are not those special words, the body compiles with errors reported.

I am still right that if I leave those two words but delete any character from the REM lines, the body also compiles with errors reported.

I count 2938 characters in the REM lines.

I hope some developer looks at this and says "Ah Hah!" It sure looks like a very odd bug to me.

Okay. We'll fix it.

So I'm guessing this did not make it into 7.0.3?

I think I'm running into this or something very similar due to large comments in the package header.

The original problem was fixed in 7.0.3, but there was an unrecognized problem when the comment text before the package includes keywords. This will be addressed shortly.

Marco,

Sorry, what I should have said was that I'd noticed the initial problem before 7.0.3 but it seems to be working nicely now that I'm on 7.0.3. My apologies if someone thought I was saying they didn't fix the originally-reported bug.

Hopefully you can find and fix latest nuance quickly and release a patch for those suffering from it.

Best,

The problem referenced here used to be gone (in 7.0.3?), but now it seems like it's back in 7.1.

The problem is having a large number of (comment) characters at the beginning of a package body. When compiling that package, PLSQL Developer will instantly come back with "Compiled succesfully", but nothing will actually have been compiled.

If you get the number of characters just right (2828 characters in 59 lines, in my case), it will also truncate the package name shown in the tab of the program window.

Please look at (re-)fixing this problem. I was so happy when it was fixed before!

If you can send me the package by e-mail, we'll check it out.