Ok, I will change this in v3. Given your statement, my understandingis that I should avoid adding checks to make sure a valid driverobject was given as the stack trace information is all the handlingthat is needed. If there is any further logic needed in that rule,could you elaborate so that I don't make this mistake in the future,or so that I don't add a check on a driver object in a case that Ishould?