Since the DEFAULT can be an expression, parentheses are legitimately possible. But for the writer of PLDoc, trying to recreate a 100% compliant SQL *and* PL/SQL parser is expecting a lot.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PLDoc-parser has problems, if input-parameter(s) of functions or procedures in packages do have a DEFAULT-value defined.
example:
FUNCTION Test
( I_ID IN NUMBER
, I_Name IN VARCHAR2
, I_CDate IN DATE DEFAULT SYSDATE
)
RETURN VARCHAR2;
I do not have any problems with that example (pldoc 0.8.2):
create or replace package xxx as
FUNCTION Test
( I_ID IN NUMBER
, I_Name IN VARCHAR2
, I_CDate IN DATE DEFAULT SYSDATE
)
RETURN VARCHAR2;
end;
Sorry for that massage, we had a typo.
...DEFAULT(2)
By writing '...DEFAULT 2' or '...DEFAULT '2' ' everything is ok.
The only amazing thing is, that our package was valid. In Oracle-docu I haven't found any entry for that syntax.
Sorry again, and thanks a lot for your answer
Since the DEFAULT can be an expression, parentheses are legitimately possible. But for the writer of PLDoc, trying to recreate a 100% compliant SQL *and* PL/SQL parser is expecting a lot.
There was a little nasty error that caused this problem.
Registered bug 1028068.
Fixed in CVS.
When the next nightly release will be created, the fix will be there.