In article <#H*************@TK2MSFTNGP11.phx.gbl>, Dmitriy Lapshin [C# / .NET MVP] wrote:
Hi all,
I think the VB .NET compiler should at least issue a warning when a function
does not return value. C# and C++ compilers treat this situation as an error
and I believe this is the right thing to do. And I wonder why VB .NET keeps
silence and makes such function return some default value instead. Isn't it
error-prone?
Yes it is error prone, and I agree with you. I don't know if this is an
attempt to stay compatible with VB.CLASSIC code - but I wish there was
at least an option to change this behavior.
--
Tom Shelton
MVP [Visual Basic]