Remaining non-blind macros

[Eric Blake]

I just looked at the list of blind macros (those that must be
passed arguments to be recognized, such as define), and had
a couple of questions.  Most of the builtins that are not blind
have a reason; for example, dnl would be worthless if it were
blind.  And I already recently changed indir and format to be
blind.  However...

Any reason that shift is recognized even without arguments?
It is a common English word, but currently gets eaten when
it appears alone.  Also, it is normally used as shift($@), and
since it discards the first argument, it almost makes sense
to require a first argument.  Would it cause anyone heartache
if I changed shift to be blind?

What about m4wrap?  Because of the prefix, it is less likely
to appear in ordinary text.  But it really makes no sense to
wrap nothing; should I change it to be blind?

-- 
Eric Blake