Chris Quenelle 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.
So converting lock_lint to support warlock features is not a very
good idea.
I hope we can add more features into warlock so that warlock could
also do
what lock_lint does, and further what lock_lint does not. Remember
warlock
is not just for kernel and there are no known lock_lint users today.
I know lock_lint is made a product of Sun, and if we make warlock
capable of
what lock_lint can do there is maybe duplicated work. Do you have any
good
idea and suggestions?
If what you say is true, then we should consider supporting warlock as
part of Sun Studio. It would help to make this case if there were more
warlock users. (Which we can get by making it available to the public)
There is definitely going to be more warlock users, and we even want to make
"warlock clean" an item in C-Team checklist. So take this possibility to
your
consideration.
Aaron
--chris
_______________________________________________
tools-discuss mailing list
[email protected]
