# from Michael G Schwern
# on Saturday 19 April 2008 08:15:
>The prefixing solution sucks, but it's all we have... and that's a bad
> place to be. Rather than arguing about a sucky solution, does anyone
> have another solution to offer?
I'm not sure what you mean by "prefixing"[1], or what sucks about m/\./
being a straightforward identifier for user keys.
sloppy.
.better_but_lazy
.org.vectorsection.officially_registered
.File-Fu.perl_domain
That is, the recommendation is that user keys start with a '.', but the
condition which guarantees that it will never clash is simply that
$key =~ m/\./.
The further suggestion is that to avoid conflicts, the keys start with a
prefix which is registered or claimed in some way.
Of course, I would want strict key checking to be off by default and
enabled only by the 'strict' pragma. But conveniently: the pragma is
declared by the tap stream (i.e. emitter.)
[1] If prefixing means "one prefix to rule them all", or "every builtin
starts with 'tap_'", or "X-" -- then yes, that sucks. I think
alternatives which move the clash-prevention information out of the key
text suck more though (then you get into some sort of namespace
declaration, context, etc.)
--Eric
--
Hot dogs: just another condiment.
--Heart-attack Man
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
