Subject: ll files using the load subcommand.

From: "Johnston Phil" <[email-masked]>
Date: Tue, 20 Mar 2007 20:23:33 -0600

Using the disallow subcommand to disallow all sequences that reach a function will also cause a message that the function is never called.
However, if LockLint is not told about this coverage relationship, it assumes that the locks are being used according to the usual conventions and generates error messages.
You can even refer to it simply as bar as long as there is no other variable by that name.
This is treated analogously to the previous case; the index is ignored.
Lists information about the locks of the loaded files. ] Tells LockLint to exclude certain functions and variables from the analysis. If read is not present, the side effect specifies that the function acquires write-level access for that lock. TABLE A-2 lists the exit status values of LockLint subcommands.
See LockLint Naming Conventions for details on specifying names to LockLint subcommands.
Upon exiting the Korn shell, the LockLint context is removed. Also, any writes to read-only variables are reported.
A root function is a starting point for the analysis; functions that are not called from within the loaded files are naturally roots. Diese Software ist Open Source, und wird von einigen Nutzern des Wikis weiterentwickelt. covers, asserts that a given lock protects another lock; this is used for hierarchical locking schemes.