Re: General purpose notification mechanism for Lua

[Doug Rogers <doug.rogers@...>]

Doug Rogers wrote:
> I like the signal:stop() idea. I usually use return values to stop
> further processing. Your way is more explicit.

On further review I noticed that the signal is not passed to the
handler. I think it would be better if the signal were always the first
parameter to the handler. Otherwise the handler can only be used with a
single globally accessible signal.

Also, the 'test' link at http://wiki.github.com/katcipis/Luanotify/api
after Signal Class should be updated to match the new name
(test_signal.lua).

Doug


______________________________________________________________________________________
The information contained in this email transmission may contain proprietary and business 
sensitive information.  If you are not the intended recipient, you are hereby notified that 
any review, dissemination, distribution or duplication of this communication is strictly 
prohibited.  Unauthorized interception of this e-mail is a violation of law.  If you are not 
the intended recipient, please contact the sender by reply email and immediately destroy all 
copies of the original message.

Any technical data and/or information provided with or in this email may be subject to U.S. 
export controls law.  Export, diversion or disclosure contrary to U.S. law is prohibited.  
Such technical data or information is not to be exported from the U.S. or given to any foreign
person in the U.S. without prior written authorization of Elbit Systems of America and the 
appropriate U.S. Government agency.