jsdoc and pseudo-namespaces? about jsdoc

[micmath]

This probably does what you mean in JSDoc 3, but are you saying you would rather not have to document the "my" namespace on it's own?

/**
* Document me.
* @namespace my
*/

/**
* My special namespace
* @namespace my.namespace
*/
$namespace('my.namespace', /** @lends my.namespace **/ {
   /**
    * Foo - does something really neat...
    */
   foo: function() {
   }
});

That fixes the issue. I didn't realise that all namespaces in the chain had to be documented. I think that it would be beneficial for jsdoc to fill in the blanks with simple generic pages. A little like phpDoc does.

The information on (http://code.google.com/p/jsdoc-toolkit/wiki/TagNamespace) is confusing because it suggests that @namespace is only followed by a description, when in fact it is followed by the name of the namespace (which makes more sense to me).

Was this a specific change to jsdoc3 or an error in the jsdoc2 wiki?

[micmath]

You are correct, the @namespace name syntax was added in JSDoc 3, and will be documented here (soon):
http://usejsdoc.org/tags-namespace.html

The difficulty with creating generic pages for undocumented parts of the chain is that, in JavaScript, those pages could refer to almost anything (class, namespace, module, even function or variable), and this gets tricky with very long chains and chains like @namespace foo.bar.Zop#ns. In other words it's simple in the simple case, but there probably isn'y any good way to do it in the complex case. I do understand the desire to have something like that but on the other hand I don't particularly want to make it easy for people to skip documentation for things like root namespaces either.

Many thanks for your help. Keep up the great work with jsdoc3!