On 4/29/09 5:54 PM, Tarmik wrote: > I haven't analyzed by myself yet what kind of output dehydra produces > - but I would guess it's something fetched to output - plain text.
dehydra itself only has basic functions: print() (prints a location along with a message) _print() (prints text without any location formatting) warning() error() read_file() write_file() There are all documented at https://developer.mozilla.org/en/Dehydra_Manual > Question - Do you have / do you know any good framework / scripts, > which can generate for example .html as output, from where you can see > the summaries of your project (e.g. errors, warnings, etc...) and by > following the link - going deeper into the problematic of your code. I do have a set of scripts which take GCC compiler warnings (both the builtin ones and dehydra-generated ones) and saves these to a database. It then has a web frontend. The web frontend for Mozilla compiler warnings: http://office.smedbergs.us:8080/ The buildbot script which parse compiler warnings into a database: http://hg.mozilla.org/users/bsmedberg_mozilla.com/static-analysis-buildbot/file/f1daae53f5ce/warning-parser.py The python web frontend: http://hg.mozilla.org/users/bsmedberg_mozilla.com/static-analysis-buildbot/file/f1daae53f5ce/warning-ui/ > (P.S. do you see also that dehydra's output format could be somehow > formatted differently also in similar manner to lint ? (E.g. create > dehydra's base .js module which would be responsible for outputting, > and format of output) ) > all other's .js uses that base module. The analysis script can format the output any way it wishes. You could certainly create a common library of formatting functions as a separate .js file and include() that. --BDS _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
