> You miss the point here. If the value returned is sometimes VOID and > sometimes 0, then if you do: > > if( voidP( result ) ) then > -- do something > else if( result = 0 ) then > -- do something else > end if > > Then you will get different results depending on the apparently random > output from this function with a single known input. That's not good from > an engineering POV.
Ah, but you will get consistent results with your code. You're testing for void first, just like I found I needed to do. That's the whole point. Void is, by definition, undefined--nothing. Not zero, not false. Good coding practice is to check to make sure the variable is initialized (not being initialized is the most common reason for a void return). I agree, maybe MM could have handled it in their code better, and given us consistent returns. OTOH, they have provided us with a workaround. Check for voidP and everybody's happy. Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
