Zacru
Joined 10 years ago
Karma
57
Submissions
41
Member since
Apr 8
Joined 10 years ago
I would say one good reason is that
waitlock myapp &
JOB_PID=$!
# ... do exclusive work ...
kill $JOB_PID
is a lot easier to use and remember than (; flock -n 9 || exit 1; # ... commands executed under lock ...; ) 9>/var/lock/mylockfileMaybe there should be some minimum distance between all of the choices.
Of course if they do, I hope they will say "either modified Apache or the GPL".
My company's lawyers made a big stink about us using jQuery plugins that said "and" instead of "or".
This is actually an option in the settings (on desktop, at least).
I don't see this in the example. Closure #1 is never bound in the scope, as far as I can tell. Could you explain how closure #1 is closed over without being bound?