Not a programming question...
-
In visual studio 2005 is there an option to specify the depth of the "call stack" window.
-
In visual studio 2005 is there an option to specify the depth of the "call stack" window.
This is an IDE question, but, why would you want to ? Why would you not want to see the whole stack ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
This is an IDE question, but, why would you want to ? Why would you not want to see the whole stack ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Because the stack might be zillion levels deep (with reason), but VS2005 will just grind to a halt and exit. I have seen this happen a lot. :(
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." -
Because the stack might be zillion levels deep (with reason), but VS2005 will just grind to a halt and exit. I have seen this happen a lot. :(
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."leppie wrote:
Because the stack might be zillion levels deep
:~
My head asplode!
Calling all South African developers! Your participation in this local dev community will be mutually beneficial, to you and us.
-
Because the stack might be zillion levels deep (with reason), but VS2005 will just grind to a halt and exit. I have seen this happen a lot. :(
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." -
leppie wrote:
Because the stack might be zillion levels deep
:~
My head asplode!
Calling all South African developers! Your participation in this local dev community will be mutually beneficial, to you and us.
Welcome to recursive programming, now add tail calls, and you dont have a clue where you are on the stack :)
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." -
Welcome to recursive programming, now add tail calls, and you dont have a clue where you are on the stack :)
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."Recursive programming and tail calls :~ Now that's scary. Actually not as scary as a third year exam question I had, which had to be answered in pen on paper, in C++, to traverse a tree (I forget which type of traversal), without using recursion. Much of the course had focused on introducing and exploring recursion. I had also forgotten to take a pencil, so this question resulted in a lot of very iterative scribbling. :-O
My head asplode!
Calling all South African developers! Your participation in this local dev community will be mutually beneficial, to you and us.
-
Recursive programming and tail calls :~ Now that's scary. Actually not as scary as a third year exam question I had, which had to be answered in pen on paper, in C++, to traverse a tree (I forget which type of traversal), without using recursion. Much of the course had focused on introducing and exploring recursion. I had also forgotten to take a pencil, so this question resulted in a lot of very iterative scribbling. :-O
My head asplode!
Calling all South African developers! Your participation in this local dev community will be mutually beneficial, to you and us.
Argggg, I hated those! :)
xacc.ide
IronScheme a R5RS-compliant Scheme on the DLR
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."