> I hate to turn off strict. Why use strict if you are only going to turn it off ?Strict is a safety feature. It is there to prevent you from accidentally doing something dangerous. Like all safety features, it also prevents some things that are not really dangerous. For example, sometimes my kitchen smoke alarm goes off when I am cooking onions.
If what you want is to do something that is not dangerous, but which the alarm is too stupid to distinguish from dangerous behavior, it is entirely appropriate to turn off the alarm. Should I stop cooking onions, out of some superstitious fear that maybe the alarm knows better than I do? No, that would be ridiculous.
You asked why have the alarm, if I am just going to shut it off? That is the wrong question. I am not going to shut it off all the time; just when it interferes with my cooking of onions. The rest of the time, it will be available to perform its function, which is to warn me about accidental fires.
The alarm is a means to an end. The goal is to prevent fires. Keeping the alarm quiet is not a goal in itself; it is only a way to help prevent fires. Keeping strict quiet is not a goal in itself, either. The goal is to avoid the dangerous and difficult bugs that can result from careless use of symbolic references. No dangerous problems can occur in this case.
But apparently a lot of people in this thread feel the way you do, because we've seen a whole bunch of clumsy, overcoded solutions, all just to get around turning off the smoke alarm, when what's really wanted is just to turn off strict for one line and cook the damn onions already.
In reply to Re: use slack;
by Dominus
in thread use slack;
by epoptai
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |