Should the generate macro be renamed? about hardwrap HOT 2 CLOSED

I agree that the current names are a bit cumbersome and unwieldy. Initially I was against your suggested change because if someone provided an invalid first argument, then they wouldn't have the relatively clear Undefined control sequence. error. However, on further consideration, I think it works in our favor because we could provide a better error message ourselves and it allows for future expansion (in case the need ever arises for a non-package and non-class error message).

We should be friendly and allow for case-insensitive checks against that first argument so that 'Class' and 'class' both work. It's unambiguous for us and reduces mental overhead for the class/package developer.

from hardwrap.

create wrapper command \GenerateLogMacros

closed by f767336

from hardwrap.