I don't think anybody tries to write code that needs to be aborted.
A possible compromise might be to implement the
enableabort statement that would support the Command-Period aborting so that you could include it at the beginning of a procedure while developing it. It would enable the abort scheme as long as the procedure is running or until a
disableabort is issued. This would be the reverse logic as Panorama 6 were the Command-Period was automatically enforce unless the
disableatort statement deactivated it.
Since code in Panorama 6 would use the
enableabort statements in that order it should not effect their code at all. The
disableabort would have no effect since it is disabled already by default and the
enableabort was used when it was specifically requested and it would be automatically dismissed at the end of the procedure.