First use - many parse exceptions

[Martin J. Evans]

Hi,

Only recently came across pldoc and it looks just what I was after.
However, when I point at one of my packages it fails with many parser exceptions.
Here are a few:

ALTER SESSION SET PLSQL_WARNINGS='DISABLE:PERFORMANCE';
      not expecting session after alter

PROCEDURE p_test(
                paid account.account_id%TYPE,
                pamount account.balance%TYPE,
                ptype transaction.transaction_type_id%TYPE,
                pbid xxx.xxx_id%TYPE,    -- may be NULL
                pmid market.market_id%TYPE, -- may be NULL
                ptxn_desc transaction.description%TYPE) as

does not like transaction.transaction_type_id%TYPE

There are a number of others when I comment the above out.
Have I just been unlucky here?
Are people still using pldoc with their Oracle packages/procedures?

Martin

[Albert Tumanov]

Currently, pldoc can only parse package specifications,
not package or procedure bodies.

[Martin J. Evans]

Thanks Albert, I thought there was something I'd missed.
So, running on my package spec file reduces the issue to:

net.sourceforge.pldoc.parser.ParseException: Encountered "transaction" at line 10, column 35.

    PROCEDURE p_debitAccount(
                            paid account.account_id%TYPE,
                            pamount account.balance%TYPE,
                            ptype transaction.transaction_type_id%TYPE,
                            -- proceding line in error
                            pxxx xxx.xxx_id%TYPE,
                            pmid market.market_id%TYPE,
                            ptxn_desc transaction.description%TYPE);

Any way around this? I can't easily change my table and column names.

Martin