Constants in a package

[deniskeen]

In SQL/Developer 5.x it was possible to
expand/collapse the list of constat
declarations in a package (in program window)
Now this feature is absent
It's very inconvenient if there's a lot of constat declarations in a package.

Denis

 

[Marco Kalter]

We will make a preference for this to have the declarations in separate folders again. This is on the list of enhancement requests.

 

[Eric Prudhon]

Hello,

As I cannot find any related preference, is this enhancement available in 6.0.5?
We have just migrated from 5.x, and the lack of this feature is quite annoying as we have many packages with a lot of constants/types declarations (more than one page), and they are definitively not references for source navigation, at the opposite of functions/procedures.

Thanks
Eric

 

[Marco Kalter]

This will be added for the upcoming 6.1 release, later this year.

 

[Ed Holloman]

Hi,

I've been using a number of package level constants/variables in the package body recently and have been missing this feature in 6.x.

Looking at a coworker's version of 5.4.x, it appears that constants and variables appear in their own folder at the top of the package body contents.

I don't know how 5.4.x handled forward declarations, but it would be nice if anything in the declaration section could optionally be displayed in its own folder. It's hard to distinguish where forward declarations end and the implementations begin, besides taking up a lot of vertical real estate.

Thread 'Forward declarations' from 01-05-2005 requested a visual indication of forward declarations, which would also be nice, but if I had a choice, I'd prefer the folder option.

Thanks,

Ed Holloman

 

[orca777]

Yes i aggree - forward declarations
should be in another folder

Carl

 

[Marco Kalter]

The variables, constants, and so on have been moved to a separate folder. We will check if forward declarations can be added as well. They are indeed not the most frequently used part of the Code Contents.