© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I still don't see the use.
The client identifiers are clearly namespaced (C-style) by the "mir_" prefix already. Hence they're already unambiguous.
It's just a matter of risk. You're solving a problem that will probably never exist. That is someone defines a "mir_connect" elsewhere. And the trade-off is that the code is made uglier for this highly unlikely situation.
Taking it to an extreme, someone could still come along and define:
somethingel
albeit even less likely than the previous case. We're talking about highly unlikely vs exceedingly unlikely. So I would prefer to err on the side of code cleanliness.