Claus Pedersen
Member³
When using different Java editors, the code completion is often so intelligent that the right choise pops up as the first or second in the code completion list.
E.g. if I write
and press code completion after the dot, the code completion should know that the only objects inside myPack that can be used in this context are functions, constants, variables etc., i.e. these should be listed at the top of the list. Procedures, exceptions etc. should be listed below, seperated by a solid line, because they can not be used in this context.
Similar, if I write
and press code completion, the procedures should be listed first.
This method should be applied for dates, booleans, records, exceptions etc., i.e. methods, variables, constants etc. of the specified type should be listed first.
I know there is a problem with numbers/varchars because PL/SQL is relaxed with respect of type conversions, but the code completion should still make an intelligent guess, so if my variable is a number, the functions returning a number should be listed first, then the functions returning a varchar, but the functions returning a date or a record should be below the line, because they can not be applied here.
E.g. if I write
Code:
i := myPack.Similar, if I write
Code:
myPack.doSomething;
myPack.This method should be applied for dates, booleans, records, exceptions etc., i.e. methods, variables, constants etc. of the specified type should be listed first.
I know there is a problem with numbers/varchars because PL/SQL is relaxed with respect of type conversions, but the code completion should still make an intelligent guess, so if my variable is a number, the functions returning a number should be listed first, then the functions returning a varchar, but the functions returning a date or a record should be below the line, because they can not be applied here.
