Closed joeced closed 6 years ago
Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
bug fixes to 0.2
re.sub()
to scan code for functions with ellipsis in signature, Pygments
lexes these as Token.Error
, but classdefs are OK, and everywhere else Pygments sees
them as comments and concatenates everything afterword, which is what they are. This
effects property defaults that are arrays and span multiple lines (issue #11) that do
use ellipsis, if the ellipsis also had comments, then replacing ellipsis everywhere in
code would leave uncommented text and cause Pygment lexer errors, need to replace them
in all classdef methods (anywhere function keyword occurs), so just checking first line
would not workMatObject
class attribtutes for basedir
, env
, app
& dbg
so that can issue warnings for exceptions instead of causing build to fail, as
well as verbose feedback during matlabificationOriginal comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
bug fixes to 0.2
re.sub()
to scan code for functions with ellipsis in signature, Pygments
lexes these as Token.Error
, but classdefs are OK, and everywhere else Pygments sees
them as comments and concatenates everything afterword, which is what they are. This
effects property defaults that are arrays and span multiple lines (issue #11) that do
use ellipsis, if the ellipsis also had comments, then replacing ellipsis everywhere in
code would leave uncommented text and cause Pygment lexer errors, need to replace them
in all classdef methods (anywhere function keyword occurs), so just checking first line
would not workMatObject
class attribtutes for basedir
, env
, app
& dbg
so that can issue warnings for exceptions instead of causing build to fail, as
well as verbose feedback during matlabification
Originally reported by: Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown)
if functions have no return value autodoc crashes with