Re: How can I document PL/SQL Libraries in Forms 4.5?

From: Steve Cosner <stevec_at_zimmer.csufresno.edu>
Date: 20 Feb 1999 00:05:42 GMT
Message-ID: <7aku8m$gk$1_at_nntp.csufresno.edu>

Don't call your solution a kludge. It works pretty well here.

In Forms, I have used a form-level trigger named AA_READ, and a procedure of the same name could be used in your PLL library. All you need in each is one valid command:
  Null;
And the rest can be comments. I just put a /* at the top, and terminate the trigger or procedure with */ at the bottom.

Steve Cosner

---

http://members.aol.com/stevec5088
Downloadable Quick Access utility form: Display and update any table.

In article <slrn7crb5m.nsk.bmessick_at_shell.clark.net>, Bill Messick <bmessick_at_clark.net> wrote:
>In our source files for PL/SQL procedures stored in the database, we have
>at the beginning a standard comment block where we identify the module, the
>author, the revision history, all the normal stuff. I want to do the same
>thing with our Forms PL/SQL libraries. But any comments that aren't
>emedded within a module definition in the library are stripped out when the
>PLD file is converted to a PLL. Does anyone know of a way to do this? I
>thought of creating a dummy procedure at the top of the file:
>
>PROCEDURE documentation_kludge IS
>--"
>--" MODULE: formlib.pll
>--"
>--" AUTHOR: Bill Messick
>--"
>. . .
>--"
>BEGIN
> NULL;
>END;
>
>but I was hoping there would be a more straightforward solution.
>
>--
>Bill Messick
>Consultant
>Computer Associates Global Professional Services
Received on Sat Feb 20 1999 - 01:05:42 CET