And how would it differ from END?
Like CHECKs, ENDs execute in reverse order. Which generally means that main END executes before module ENDs (unless we're careful to put our main END before our module loads -- which is subtle and counterintuitive). Sometimes it would be handy to be able to mark some cleanup code so that it executes before main's END, regardless of how early main's END is declared.
You can't predict when the last time a module is going to get used...
I'm not suggesting you need to. I'm saying that, just as all UNITCHECKs are guaranteed to run before any main CHECK, we might want a UNITEND that's guaranteed to execute before any main END.
Damian
