> I can change the error to something like
> 
> "Intrinsic function NULL() cannot be an actual argument to
> STORAGE_SIZE because it returns a disassociated pointer”

I think that’d be better, indeed.


> No.  This isn't a numbered constraint.  I spent an hour or so
> tracing though parent namespaces and symbol trees to see if
> I could catch the problem in comment #2.  I think that this
> would require a runtime error (or adding an internal attribute
> that explicitly tracks associate/disassociation and
> allocation/deallocation).

That seems likely.

Thus: OK to commit with adjusted error message (and testcase pattern).

FX

Reply via email to