comment on

There's no difference between receiving an alarm that was sent via alarm or via kill. What makes you think that the latter can trigger signals when the former can't?

I didn't say that there was a difference. I explained very clearly how to use the alarm signal in a normal application. A signal is a "message" from the OS.

What's obfuscated about sending a signal with kill, whose very purpose is to send signals?

What is obfuscated is this "poetry" idea and using language constructs in "unnatural ways". I have no problem with strange code as an art form.

In reply to Re^5: Signals in Strawberry Perl: Name or number? by Marshall
in thread Signals in Strawberry Perl: Name or number? by bv

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks