On Fri, Sep 03, 2004 at 03:45:41PM -0600, why the lucky stiff wrote:
| look, we're only trying to sensibly turn the shortcut syntax into a
| clash-free environment for the external types. i don't see why builtin
| types and user's private types can't share the generic namespace.
| ruby's default namespace contains both builtin and user-made classes.
That's also true in the Python environment. It just doesn't have
reserved keywords. In fact, if you want to really mess with someone's
brain, you do...
(True,False) = (False,True)
So, you're proposing that we leave the !stuffs ambiguous; as YAML adds
types, they go there. And a parser could, by default, load its handlers
there. But, private types could go there too. To make this "easier" for
those making private types, we follow David's suggestion:
On Fri, Sep 03, 2004 at 04:57:33AM +0100, David Hopwood wrote:
| I'm going to keep banging on about the issue of additions to the YAML
| tag repository. If there is a policy of restricting new names in the
| repository to, say, [a-zA-Z0-9_]+, then people can choose to use private
| names that do not match that regexp without any risk that they will be
| confusable with future repository-defined tags. (This is useful despite
| the fact that there is nothing preventing collisions between two private
| names in general.)
So, while people could use private tags, we'd clearly say that they
could make something that would collide with us down stream if
they used a tag from the regex given.