incubator-xap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Turyn" <MTu...@nexaweb.com>
Subject RE: AbstractTagImpl.fireEvent() argument order
Date Sat, 14 Oct 2006 05:48:40 GMT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>RE: AbstractTagImpl.fireEvent() argument order</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=2>That seems o.k., except that I'd rather not encourage the JS-oid
tendency to leave off arguments, especially as null != &lt;undefined&gt;.<BR>
<BR>
I personally don't mind putting in two null arguments, regardless of where they are; why not
keep &quot;fireEvent&quot; for a two-argument method, and something better (I don't
feel like suggesting something right now, given that I just remembered that Icame up with
&quot;AbstractBlackBoxWidgetBridge&quot;) for the full-argument version?<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>

Mime
View raw message