J
Joergen Bech
On Mon, 25 Jun 2007 20:51:35 +0200, "Herfried K. Wagner [MVP]"
---snip---
Here are some arguments, straight from the VB Compiler Dev Lead:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=137941&SiteID=1
As he says, they are aware that people want it. Just not sure how
they could implement it.
....
If you look up the topic about missing procedure view in MSDN Library,
it is stated that this is by design and basically that you should get
used to using outlining (which you yourself have pointed out in the
past). It is easy to collapse everything in a module, then expand
just the function(s) you want to look at.
....
One disadvantage of breaking everything into tiny subtasks is
that you end up with classes containing *lots* of functions, making
it difficult to tell which are the top-level ones. I have gotten used
to using partial classes - sometimes up to four or five per class -
to make it easier to browse my classes. I am not a big fan of
outlining, I'll admit, so the introduction of partial classes in 2005
was what I had been waiting for.
The biggest reason why *I* don't feel the need for this function
is that I am far more likely to scroll up and down to see supporting
functions than I am to look at a single function at a time. For those
who insist on writing a few large functions instead of breaking them
down in many small functions, I can see why the procedure view
would be useful. For me, it would just be a pain.
(And before you say that my code might not be properly refactored
if I need to jump up and down my source file: Sometimes I just need
to read the whole thing in large chunks to verify that everything is
consistent.)
....
Questions: If VB6 had never been, would people still be asking for
this feature? With outlining and partial classes as alternatives, is
there a real need for it? Is it found in other languages - and if not,
what do those programmers do?
Regards,
Joergen Bech
---snip---
Here are some arguments, straight from the VB Compiler Dev Lead:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=137941&SiteID=1
As he says, they are aware that people want it. Just not sure how
they could implement it.
....
If you look up the topic about missing procedure view in MSDN Library,
it is stated that this is by design and basically that you should get
used to using outlining (which you yourself have pointed out in the
past). It is easy to collapse everything in a module, then expand
just the function(s) you want to look at.
....
One disadvantage of breaking everything into tiny subtasks is
that you end up with classes containing *lots* of functions, making
it difficult to tell which are the top-level ones. I have gotten used
to using partial classes - sometimes up to four or five per class -
to make it easier to browse my classes. I am not a big fan of
outlining, I'll admit, so the introduction of partial classes in 2005
was what I had been waiting for.
The biggest reason why *I* don't feel the need for this function
is that I am far more likely to scroll up and down to see supporting
functions than I am to look at a single function at a time. For those
who insist on writing a few large functions instead of breaking them
down in many small functions, I can see why the procedure view
would be useful. For me, it would just be a pain.
(And before you say that my code might not be properly refactored
if I need to jump up and down my source file: Sometimes I just need
to read the whole thing in large chunks to verify that everything is
consistent.)
....
Questions: If VB6 had never been, would people still be asking for
this feature? With outlining and partial classes as alternatives, is
there a real need for it? Is it found in other languages - and if not,
what do those programmers do?
Regards,
Joergen Bech