Constants in Jumps list

Previous topic - Next topic

bigsofty

Shouldn't CONSTANT definitions be in the Jumps list tab, for a file? It makes it slightly more awkward to locate their definition otherwise.
Cheers,

Ian.

"It is practically impossible to teach good programming style to students that have had prior exposure to BASIC.  As potential programmers, they are mentally mutilated beyond hope of regeneration."
(E. W. Dijkstra)

Kitty Hello

hm. You can put a sub __CONSTANTS__ before them. That's what I do. Not nice, though. If you have every constant in the list, it might overflow for large projects.

bigsofty

What's the limit on the tree before an overflow?
Cheers,

Ian.

"It is practically impossible to teach good programming style to students that have had prior exposure to BASIC.  As potential programmers, they are mentally mutilated beyond hope of regeneration."
(E. W. Dijkstra)

Kitty Hello

screen height. I mean visual overflow.

bigsofty

How about putting constants in their own branch, collapsed by default?
Cheers,

Ian.

"It is practically impossible to teach good programming style to students that have had prior exposure to BASIC.  As potential programmers, they are mentally mutilated beyond hope of regeneration."
(E. W. Dijkstra)

Slydog

Or add CONSTANTS to the 'Go to definition' context menu option.
While you're at it, how about adding TYPES to this list also?

This would make locating CONSTANTS and TYPES so much easier.
Right now I hi-light the CONSTANT (or TYPE name) and do a search all files command (<CTRL>+<SHIFT>+<F>) and locate the definition by hand.
My current project (WIP) :: TwistedMaze <<  [Updated: 2015-11-25]