problem above: Using .c instead of .cpp: some problems fade away. Question: How is it possible to analyze code with de/tree hydra ? You're providing scripting capabilities, but not the actual code analyzer ? Is that correct ?
E.g. if I have code similar to: int* p=NULL; *p=5; - how such crashes can be detected by static analysis ? Other programs similar to lint - I guess with dehydra it should be relatively simple to write lint.js ? Correct or not ? _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
