I'm setting up templates for use by the development team, these templates include plsqldoc tags.
Part of the process is generating example documentation with the tags insitu so I can give specific examples to the developers.
Many of the function/procedure headers have revision history with multiline "comments".
Generating and reviewing documents I see exhibits like this :
:cr. REVISIONS::cr. DATE AUTHOR DESCRIPTION:cr. ---------- ---------------:cr. 03/05/2012 SXH Example yadda yadda..
I've tried with and without , the above is with, and the same run-on line is obtained
If I look at any of the source tables in Oracle and see the code as I'd expect, comments are multi-line
i.e. in user_source the line breaks are as expected
How is plsqldoc obtaining and interpreting the source text?
I thought maybe I was seeing Unix/PC formatting issue but that does not appear to be the case, I've compiled with the source saved in both flavors and the same result is obtained
Part of the process is generating example documentation with the tags insitu so I can give specific examples to the developers.
Many of the function/procedure headers have revision history with multiline "comments".
Generating and reviewing documents I see exhibits like this :
:cr. REVISIONS::cr. DATE AUTHOR DESCRIPTION:cr. ---------- ---------------:cr. 03/05/2012 SXH Example yadda yadda..
I've tried with and without , the above is with, and the same run-on line is obtained
If I look at any of the source tables in Oracle and see the code as I'd expect, comments are multi-line
i.e. in user_source the line breaks are as expected
How is plsqldoc obtaining and interpreting the source text?
I thought maybe I was seeing Unix/PC formatting issue but that does not appear to be the case, I've compiled with the source saved in both flavors and the same result is obtained