On Wed, Apr 04, 2007 at 11:50:32AM +0800, Aaron Zang wrote: > The main difference between lock_lint and warlock is that warlock (actually > wlanalyze which warlock calls and does the main job) has a command line > interface which can be used to accept a command file (.wlcmd files in > ON source tree). This is because warlock is written as a shell script but > lock_lint is written in C. And this command line interface is critical to ON. > If we want lock_lint to provide the same interface, the design is very weird > and ugly. I think Alexander has already mentioned that.
Is ON the only consumer of warlock? If that's the case, we can make changes to ON to support a better interface. It's a bit of disruption, yes, but that's better than carrying on an interface that is (paraphrasing) crufty and unmaintainable. That's just to throw the option on the table, in case you thought it might not be there. It's obviously your call. Danek _______________________________________________ tools-discuss mailing list [email protected]
