![](https://secure.gravatar.com/avatar/c4fb1aecd98bbaa9856f8c421db294e0.jpg?s=120&d=mm&r=g)
On Sat, Apr 07, 2007 at 11:10:51PM +0200, Hans Hagen wrote:
Heiko Oberdiek wrote:
If the document uses \newcommand, then the user will get an error. If the user uses a package that uses the new foo, this package will probably break. ...
\let\mynamespacedprimitive=\primitive \let\primitive\undefined
And the package that wants to use \primitive? A command name cannot be defined and undefined at the same time.
\pdfsomething can be in use as well, you never knw what users have defined
Yes, but it can be considered as reserved namespace. Thus if someone writes a package using \pdfsomething and pdfTeX later introduces a new primitive \pdfsomething, the package author cannot complain.
when etex came around \protected and \unexpanded were examples of a command that had a great potential for clashes (context had both already defined but i just use saved meanings then); such is live, such is progress
And calling for unnecessary trouble and bug reports.
Yours sincerely
Heiko