Support for Oracle Objects

[rlove]

Just ran this against utPLSQL code that has several Oracle Objects such as:

/** 
 * description
 *    ut_composite_object 
 **/
create or replace type ut_composite_object force under ut_object
(
  items      ut_objects_list,

  member procedure calc_execution_result(self in out nocopy ut_composite_object),
  member function item_index(a_object_name varchar2) return pls_integer,
  member procedure add_item(self in out nocopy ut_composite_object, a_item ut_object)
) not final not instantiable
/

Only a MD file with the filename is produced. This is a feature request to support the oracle object syntax.

[martindsouza]

What do you think the @ name should be? @type is for basic types. Should we call it @object?

[jgebal]

I would use @object
@type is more approprate for PLSQL (package level) types

[jgebal]

Quick question.
The type/package comments should be inside the code (after the create type/package line) right?

[jgebal]

Also, can we have documentation for type attributes?

[martindsouza]

@jgebal Docs should be inside the package. Usually above the proc/types/constants.

See https://github.com/OraOpenSource/plsql-md-doc/blob/master/docs/javadoc-template.md for template and https://github.com/OraOpenSource/oos-utils/tree/master/source/packages for examples.

@rlove we decided on @type (see above links)