>>
>>Interesting - so Parse() throws exceptions all the way back up the chain - two in StringToNumber and two more in Int32 ParseInt32 ; TryParse() has none.
>>I prefer TryParse() evne more than I did before :=}
>
>I remember reading about TryXXX()
>
>The intent is to avoid the cost of the exception
>
>
>some reading
>- http://stackoverflow.com/questions/1282252/how-much-more-expensive-is-an-exception-than-a-return-value
>- http://blogs.msdn.com/b/ricom/archive/2003/12/19/44697.aspx

Interesting reads (especially the latter). Something I was unaware of in that (if the writer is correct): 'foreach' uses a try/finally block as well as 'using' ?

Also I wonder if it would make sense to have an alternate 'light-weight' exception that didn't build up the stack trace info.....