Why in the world doesn't the vb.net complier (1.1) throw an error when you don't return something from a function. I know it's easy to track down, but I consistently forget to return something and then go into the debugger to figure out why the value is null (nothing in VB). Is this fixed in 2.0?
posted on Thursday, February 02, 2006 10:37 PM