Enhancement request - Package editor

[Ameen]

It would be very nice if Package editor draws a line after the end of each piece of code like procedure or function. This could save our time trying to separate each procedure and function to become more readable.

 

[Vinny]

Have you tried using the package element emplates to do this? You can easily modify the templates to include line when you insert new program units within your packages.

 

[Ameen]

Package elements are usefull when I drag-drop the element into code window. But when I am writing the code (continuous writing) like this:
create package body xxx is
procedure aaa is
begin
...
end;
[TH]
procedure bbb is
begin
...
end;
I do not want to use drag-drop elements because I need to clean up or override some placeholders before continue with the actual code and this is annoying.

 

[Ameen]

Some programing languages do this by adding display-only line separator without any characters written into the code itself, like the editors in Delphi or Visual Basic.

 

[ScottMattes]

it would be nice to have

in the mean time you could setup an autoreplace string to do this while you type.

aa=/*---------------------------*/

then you type

procedure asdf
is
begin
code here
end;
aa

 

[ScottMattes]

or see this article

autoreplace with template

 

[RobertK]

Originally posted by Ameen:
It would be very nice if Package editor draws a line after the end of each piece of code like procedure or function.....

What I do is using "Custom Syntax" to highlight the words "PROCEDURE" and "FUNCTION"
and of course it applies to nested PROCEDURE/FUNCTION but in your case you really want your code to look like this ? :
(unless of course the software can distinguish a top level module from nested ones)

____________________________________________________________
PROCEDURE alpha IS
    FUNCTION f_aaa RETURN NUMBER IS
    BEGIN
      blah blah blah....
    END ;
____________________________________________________________
    FUNCTION f_bbb RETURN VARCHAR2 IS
    BEGIN
      blah blah blah....
    END ;
____________________________________________________________
    PROCEDURE p_aaa IS
    BEGIN
      blah blah blah....
    END ;
____________________________________________________________
    PROCEDURE p_bbb IS
    BEGIN
       blah blah blah....
    END;
____________________________________________________________
BEGIN
   blah blah blah....
END ;

If it is to look like the above then it makes code look "fragmented", IMO