In the real world, it would be convenient to do something like this to perform a check on optional parameters:
<cfif structKeyExists(URL, "a") IMP validateId(URL.a)>
In this regard, we can only verify the correctness of URL.a, if it exists. This will be the most useful IMP application, IMO (well, it would seem to be).
However, due to a bug in IMP implementation, this does not work: - (
I think that Daleโs claim that much longer (and incorrect) logic is easier to read than the shortened version is, of course, erroneous and based on the premise for downloading. His position is based on the idea that "someone does not know something" is a continuous state, i.e. When someone does not know anything (for example, what โIMPโ means), then they will not know this forever. It is not true. A person may not know something initially, but as soon as they learn about it, they will know about it. Therefore, the problem of not knowing how the IMP ionizer works is very short-lived.
I do not think that situations arise in which IMP is required, arise very often, but it is convenient for its use. And it would be more convenient if it worked correctly; -)
source share