Oh I guess there aren't any callers of apply() that are passing an arg to LzState.apply(), except for one caller in LzState, which looks like it slipped by accident at some point while we were figuring this out. I will just modify that to not pass an arg. <br>
<br><br><br><br><div class="gmail_quote">On Thu, May 8, 2008 at 10:52 PM, P T Withington <<a href="mailto:ptw@laszlosystems.com">ptw@laszlosystems.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Are you saying there is a case where someone is making a delegate out of these methods? I would say you should make a delegate to a 'wrapper' method that handles the argument and then calls the real method. That way you don't have to change the signature of the public API.<br>
<br>
If you have a specific example, I could elaborate.<div><div></div><div class="Wj3C7c"><br>
<br>
On 2008-05-08, at 21:26 EDT, Henry Minsky wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So I know we were discussing the general issue of making methods that are<br>
the targets of event sending obey the<br>
event protocol and accept an argument, but in the case of 'legacy' public<br>
APIs like the LzState apply() and remove methods(),<br>
which have been publicly not requiring an argument, should we be giving them<br>
an optional "ignore" argument?<br>
<br>
<br>
<br>
-- <br>
Henry Minsky<br>
Software Architect<br>
<a href="mailto:hminsky@laszlosystems.com" target="_blank">hminsky@laszlosystems.com</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Henry Minsky<br>Software Architect<br><a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</a><br><br>