Hi,
I'd be quite happy to change that if needed, but I was under the impression
that
if(bool)return
was quite valid syntax, not returning any value, but terminating the script
at that point.
It has also been used extensively throughout DynAPI, just in keyboard.js 5
times, and the check:
if(!this.e
the only browser that I've seen react to
return;
is netscape 4.05 and lower, as it has a different JS engine
all other 4+ browsers I've tried consider a undefined value as null and consequently
as false
> Hi,
> I'd be quite happy to change that if needed, but I was under the impression
> that
>
It depends on whether or not the calling function was expecting a result. In
the case of browser events, the method should always return either a true or a
false.
For methods such as specificCreate and the like, they are not requiring a
return value because the calling code does not expect one.
- Original Message -
From: "Michael Pemberton" <[EMAIL PROTECTED]>
> It depends on whether or not the calling function was expecting a result.
In
> the case of browser events, the method should always return either a true
or a
> false.
Ok, I changed it to return true.
Richard.
___
