|
Guide Contents 1. Overview 2. Operation 3. Abstract Types |
4. Function Interfaces 5. Memory Management 6. Sharing 7. Value Constraints |
8. Macros 9. Naming Conventions 10. Other Checks Contact: lclint@cs.virginia.edu |
This guide is preserved to maintain old links, but has been replaced by the Splint Manual. |
Appendix B Communication
Splint development is largely driven by suggestions and comments from users. We are also very interested in hearing about your experiences using Splint in developing or maintaining programs, enforcing coding standards, or teaching courses. For general information, suggestions, and questions on Splint send mail to splint@cs.virginia.edu.
To report a bug in Splint send a message to splint-bug@cs.virginia.edu.
There are two mailing lists associated with Splint:
splint-announce@cs.virginia.edu
Reserved for announcements of major new releases.splint-discuss@cs.virginia.eduInformal discussions on the use and development of Splint.To subscribe to a list visit http://www.splint.org/lists.html.Next: Appendix C. Flags
Contents
This guide is preserved to maintain old links, but has been replaced by the Splint Manual. | |||
|
Guide Contents 1. Overview 2. Operation 3. Abstract Types |
4. Function Interfaces 5. Memory Management 6. Sharing 7. Value Constraints |
8. Macros 9. Naming Conventions 10. Other Checks Contact: lclint@cs.virginia.edu |