Gary V. Vaughan
Gary V. Vaughan
Running LDoc always leaves a /tmp/ldoc directory, which prevents other users from running ldoc until that directory is manually removed due to `cannot write to /tmp/ldoc` error. LDoc should certainly...
LDoc can't handle non-alphanums in @fields, here: http://rrthomas.github.io/lua-stdlib/modules/std.functional.html#op Notice all the actual field names are missing, compared to: https://github.com/rrthomas/lua-stdlib/blob/master/ext/std/functional.lua#L176 I would also have liked to document metamethods according to their...
With recent updates, I explicitly list @classmod files in topological order, and that is correctly reflected in generated index.html (with `std.object` base object first): http://rrthomas.github.io/lua-stdlib/ Also, pages in `modules/*.html` are...
there's already the beginnings of LDoc markup, but we should be building and shipping LDoc html files for any modules that the user can conceivably require and make use of...
This might work already, in which case all we need is new specs to prove it. Otherwise, calling `error` with a non-string argument should be supported by the Specl `raise`...
while io redirection and capture works well for examples, it doesn't work properly when a child process is forked and interacts with io. ``` yaml - describe spawn: spawn =...
Something like this: ``` lua badargs.diagnose (func, "(argspecs) => returnspec") ```
certainly if an example takes more than a handful of seconds to complete, it has probably hung or gone into an infinite loop - it would be nice for Specl...
When _not_ using `--unicode` compatibility, Lua example code is refetched from the document source, preserving new-lines against the YAML spec. Generally, that's a useful thing, because line numbers for errors...
Currently, when Specl refetches Lua example code from spec-files to compile with sympathy for line numbers in error messages, it tries to feed YAML anchor and alias syntax to the...