If you have access to SQL*Plus, you can get the interface of a function or procedure documented with a fairly straightforward output. Just do

SPOOL output.filename DESCRIBE PROCEDURE <procedure_name> SPOOL off

This yields up output of the form:

PROCEDURE new_item
Argument Name	Type		In/Out      Default?
 ------------------------------ -------  --------------
  FOO		VARCHAR2(28)	   IN
  BAR		VARCHAR2(25)	   IN
  BAZ		VARCHAR2(25)	   IN
  NEWID		NUMBER(38)	   OUT

Which is pretty easy to parse, or may even be the sort of output you wanted in the first place. I'm sure you could even snag such info out of DBI (not that I've tried it ... )

HTH

Philosophy can be made out of anything. Or less -- Jerry A. Fodor


In reply to Re: Scanning a plsql package body to make package headers... regexp requested by arturo
in thread Scanning a plsql package body to make package headers... regexp requested by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.