Yeah, don't get me wrong. I'm not _trying_ to break fb_social or any other module. But I did by accident. :) And I might break future fb_... modules if I don't know they exist. Within modules/fb/ there are a number of modules named fb_something, and I'll create new ones as needed. -Dave On Saturday 16 October 2010 14:05:18 Daniel F. Kudwien wrote:
But isn't the entire "fb_social" namespace within the "fb" namespace?
Yes, but that's the edge-case for which no solution exists. There are various node_* or views_* or user_* modules, which all have to make sure that none of them unintentionally breaks the functionality of the "parent" namespace.
That said, "fb_social" is only able to break the "fb" namespace in case "fb" implements stuff that starts with "fb_social". Sounds rather unlikely to me, but I also don't know your code.
In any case, this namespace conflict sounds easily resolvable through a gentle agreement of both maintainers.
sun