Reworked the warnings system to allow one to specify a path pattern
to enable or disable a set of warnings only within that path.

But for classes only warn about public ones that are undocumented.

This case is now covered with the #repeatable field and gets
generated for the @since tag automatically.

Most tags don't make sense to be used multiple times - like all
boolean tags.  So I introduce a #repeatable field which must
be set to true for all tags that can be used several times
within one doc-comment.

When tag not marked as #repeatable, generate a warning
of type :tag_repeated.

The old syntax has been deprecated for a while - time to remove
support completely.

This will now break all the extensions written so far against 5.0 beta.
However, I think it's only right to provide the position information
also inside #parse_doc allowing therefore warnings to be reported
in that stage too.  And it's the right time to make this change.

Not much of a change, but at least one less instance variable.

Getting rid of lots of code scattered around all over that deals
with extracting the filename and linenr out of some hash and
passing them as separate arguments.

When using variable number of arguments it's common that the
arguments are read from `arguments` array instead of the actual
parameter variables.

Useful for reading in larger chunks of HTML or CSS.

To include additional CSS to the page.
The CSS will get appended to the CSS generated by Tag classes.

MD5-rename the file like with data.js file.
Then link it from index.html.

Also reorganize the Web::Writer class.
Save the MD5-renamed files to a local hash instead of
polluting the Options object - then pass the hash directly
to IndexHtml writer.

Cleaning up the top JSDuck namespace even more.

I always had some trouble finding all the different web-output-related
classes.

To allow for simpler way to supply the old version warning message.

Just a useful shorthand during development.

But still create no output.  Simply make it easier for somebody
to override the tag and add the output capability.

Previously when --tags option was used all the builtin tags got
loaded first and registered, after that the tags from additional
paths got loaded and registered, but loading an override for a tag
didn't trigger re-registration, effectively meaning that one could
override all the other methods of a builtin class except the
constructor - but that's the most useful thing to override.

Now when --tags option is used, the TagRegistry is reinstantiated
with list of additional load paths, and on first access to the
registry, the classes from all paths get loaded in and only after
all tags are loaded will they get instantiated, so one can also
override the constructor.

Provide just the basic info and reference the wiki guide for details.

Caused me to push out an extra beta release.

The whitespace after a tag is never useful - having each Tag
class deal with parsing that is simply a waste.

This way the color of individual p can be more easily overridden.

This file now contains more than just signature styles.

Introduce .rounded-box CSS class for the generic rounded style.
Then add additional classes to the actual divs to apply custom
styles through @css attribute.

For now the CSS just gets added to index.html file, next step would
be to move it into a separate file.