"incomplete" code completion within packages

[Benjamin L]

Code completion, does only propose and complete procedure names, if the procedure or function is within the same package.
It doesn't show the parameters after writing '(' in the Editor as it does if you call public procedures of other packages.

This Problem is the same in Developer 8 and 9 beta.

 

[Marco Kalter]

For private functions and procedures this will indeed not work. For public functions and procedures this should work just fine.

 

[Benjamin L]

Thats correct, but i think in a IDE this feature is essential. Or would you make all your procedures public, only to get help by the IDE?

 

[Marco Kalter]

We currently rely on the "describe" functionality of the Oracle Server, which only works for public procedures and functions. We will have to change this an parse the local declaration. This is on the list of enhancement requests.

 

[Benjamin L]

Thank you, this would make coding a lot easier.

 

[Claus Pedersen]

We will have to change this an parse the local declaration.

Should be a do-able task. PLD has already parsed the private methods, private cursors etc. as they are present and visible in the code content pane. Should be a question to include them in the list already given by the database.

 

[Benjamin L]

Are there any news according to this fix?

 

[Claus Pedersen]

Is this included in version 10?

 

[Marco Kalter]

No, this has not been implemented for version 10.

 

[Claus Pedersen]

Please, could you make this improvement as soon as possible, preferably in one of the beta-version for version 10? I am sure that I speak for hundreds of database package programmers, when I say that it would make a world of difference to us all to have a well implemented code completion.

It should be quite easy to merge the list of internal functions to the list of objects from the database views. The internal objects are already known by PLD, because they are shown in the code content pane (cursor parameters, private method parameters etc.)

Please also include constants, types etc. from the package header when doing code completion in the package body.

Please take another look at the rather large back catalogue of enhancements requests for code completion and try to implement as many as possible for version 10.

Also please try to make code completion work for PL/SQL arrays of records, e.g. myArray(2).myRecordColumn

Working code completion for myRecordColumn (after the end paranthesis and period) would be so sweeet...

Thumbs up for the developers!

 

[Roeland]

I support this feature request!

 

[PeterW]

Me too!

 

[Benjamin L]

Is this included in version 11?