Something I noticed when doing some size comparison compilations: The presence of an Abbreviate directive has no effect unless the -e switch (or its equivalent) is used.
Yes, that is using the tool wrong. However: How about the compiler issues a warning in that case, to indicate that the -e switch must be used for Abbreviate directives to have an effect?
Or even better: Encountering an Abbreviate directive causes the compiler to automatically enable the -e switch and warn that this was done?
Turning on -e mode automatically seems like a bad surprise all around. The existence of a manually settable -e switch may be anachronistic, but I don’t think we should deprecate it at this late date.
A warning? Maybe. Do people prefer to set up their source code with abbreviations and then separately decide whether to use them? (This is an audience question.)
I see, for example, that advent_punyinform.inf on the Archive gives abbreviations, and there’s a comment recommending -e mode, but it doesn’t include !% -e as a header comment (which would make it actually happen). Mixed messages there. What was the intention?