From: drl7x Date: Mon, 21 Apr 2003 03:19:08 +0000 (+0000) Subject: Got gmake dist to work X-Git-Tag: splint-3_1_0~5 X-Git-Url: http://andersk.mit.edu/gitweb/splint.git/commitdiff_plain/e63e0a4a31c06a56312538440dd5b384e19ddb55 Got gmake dist to work This required making sure that additional files were added to the tar ball. Also I had to fix a bug in the test sutie for db3. --- diff --git a/doc/Makefile.am b/doc/Makefile.am index f1d05f7..933d80f 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -5,7 +5,7 @@ AUTOMAKE_OPTIONS = 1.5 foreign #this is just a hack to get make dist to work. ## Include them in the distribution -EXTRA_DIST = splint.1 freebsd.html linux.html sunos.html manual.pdf faq.txt manual.css html/manual.htm html/footer.html html/header.html html/realloc.htm +EXTRA_DIST = splint.1 freebsd.html linux.html sunos.html manual.pdf manual.css html/manual.htm html/footer.html html/header.html html/realloc.htm man_MANS = splint.1 diff --git a/doc/Makefile.in b/doc/Makefile.in index 9a05c66..b4f8bf6 100644 --- a/doc/Makefile.in +++ b/doc/Makefile.in @@ -99,7 +99,7 @@ AUTOMAKE_OPTIONS = 1.5 foreign #this is just a hack to get make dist to work. -EXTRA_DIST = splint.1 freebsd.html linux.html sunos.html manual.pdf faq.txt manual.css html/manual.htm html/footer.html html/header.html html/realloc.htm +EXTRA_DIST = splint.1 freebsd.html linux.html sunos.html manual.pdf manual.css html/manual.htm html/footer.html html/header.html html/realloc.htm man_MANS = splint.1 subdir = doc diff --git a/doc/html/faq.html b/doc/html/faq.html index 5fccd2c..734c08e 100644 --- a/doc/html/faq.html +++ b/doc/html/faq.html @@ -1,407 +1,397 @@ - - - - - - - Splint FAQ + + - - + + Splint FAQ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Splint - Secure Programming Lint
 - -		 - - -info@splint.org - -
- -Download -- -Documentation -- -Manual -- -Links - - - - -Reporting -Bugs - -Mailing -Lists      -Sponsors -- -Credits - -
- + +

Splint - Frequently Asked Questions

- -

Index

  1. What is the difference between Splint and LCLint?

    +

    Index

    + +
      +

      General Questions About Splint

      +
    1. + + What is the difference between Splint and LCLint?
      +
      2. +
    2. What is the Splint logo?
      3. -

    3. What is the Splint logo?

      +
    4. Can I include Splint in my software distribution?
      5. -

    5. Can I include Splint in my software distribution?

      +
    6. Can we use your software in our company? (We are not a GNU + organization.)
      7. -

    7. Can we use your software in our company? (We are not a GNU organization.)

      +
    8. Does Splint handle C++?
      9. -

    9. Does Splint handle C++?

      + +

      Installation

      +
    10. I downloaded the Splint .tgz file but can't figure out how to + extract it. There is no 'z' option on the tar on my system.
      11. -

    11. I downloaded the Splint .tgz file but can't figure out how to extract it. - There is no 'z' option on the tar on my system.

      +
    12. I want to use Splint in win2000. How do I do that?
      13. -

    13. I want to use Splint in win2000. How do I do that?

      +
    14. I have installed Splint for Windows 2000. Where should I put + the ".splintrc" file?
      15. -

    15. I have installed Splint for Windows 2000. Where should I put the ".splintrc" - file?

      +

      Usage

      +
    16. Which compilers does Splint support?
      17. -

    17. Which compilers does Splint support?

      +
    18. How does Splint handle const?
      19. -

    19. How does Splint handle const?

      +
    20. Why do I get a warning when multiplying different integer + types? The C standard says this is ok. Why is this wrong?
      21. -

    21. Why do I get a warning when multiplying different integer types? The C - standard says this is ok. Why is this wrong?

      +
    22. The C standard says that what I'm doing is okay. Why does + Splint give me a warning?
      23. -

    23. The C standard says that what I'm doing is okay. Why does Splint give me a - warning?

      +
    24. Splint complains if I ignore the return value of scanf but + not printf?
      25. -

    25. Splint complains if I ignore the return value of scanf but not printf?

      +
    26. I develop code on an embedded system with a compiler that + uses nonstandard key words and data types. I would like to run Splint on my code + but these nonstandard keywords cause parse errors. What should I do?
      27. -

    27. I develop code on an embedded system with a compiler that uses nonstandard key - words and data types. I would like to run Splint on my code but these nonstandard - keywords cause parse errors. What should I do?

      +
    28. How can I get Splint to recognize directory trees and local + source include directories?
      29. -

    29. How can I get Splint to recognize directory trees and local source include - directories?

      +
    30. I heard that we will get lot of parse errors when we run + this tool first time. Hence we need to modify source code. Is it correct ?
      31. -

    31. I heard that we will get lot of parse errors when we run this tool first time. - Hence we need to modify source code. Is it correct ?

      -
      32. -

    32. I heard that Splint can generate some spurious errors ( not genuine errors). - Is it correct ?

      +
    33. I heard that Splint can generate some spurious errors ( not + genuine errors). Is it correct ?
      34. -

    34. When I build Splint I get the following errors.... Should I be worried?

      +
    35. When I build Splint I get the following errors.... Should I + be worried?
      36. -

    36. I just installed Splint on a new machine. I get a bunch of errors during building when the test suite is run. - When I look through the results, it seems like Splint is not reporting any errors in the code it analyzes. What is going on? -

      +
    37. I just installed Splint on a new machine. I get a bunch of + errors during building when the test suite is run. When I look through the results, + it seems like Splint is not reporting any errors in the code it analyzes. What is + going on?
      38. -

    38. I get parse errors when I try to run Splint on code like #define - MACROdebug(...) blahblah . Can I use variadic macros in Splint?

      +
    39. I get parse errors when I try to run Splint on code like + #define MACROdebug(...) blahblah . Can I use variadic macros in Splint?
      40. -

    40. I use realloc in my code. How can I get Splint in check this code more - effectively?

      +
    41. I use realloc in my code. How can I get Splint in check this + code more effectively?
      42. -

    42. I think I've found a bug in Splint. What should I do?

      +

      Bugs

      +
    43. I think I've found a bug in Splint. What should I do?
      44. -

    44. Splint tells me that there is a bug and I should report it. What information - should I send?

      +
    45. Splint tells me that there is a bug and I should report it. + What information should I send?
      46. -

    46. My question isn't answered here. How can I get more information about - Splint?

      +
    47. My question isn't answered here. How can I get more + information about Splint?
    -

    Questions and Answers

      - -

    1. What is the difference between Splint and LCLint?

      -

      Before 2002, Splint was known as LCLint. Splint 3.0 is the successor to LCLint - 2.5.

      - -

      LCLint was originally named for LCL, the Larch C Interface Language and lint, a - well-known C program checking tool. Because our tool has diverged from LCL, and our - focus now is on secure programming, it was renamed Splint. Splint's name has (at - least) three interpretations: specifications lint, secure programming lint, and first - aid for programmers. It's also easier to pronounce than LCLint.

      -

    2. What is the Splint logo?

      -

      Thomas Jefferson's Serpentine Walls at the University of Virginia. The walls are - one brick thick, but because of their design are both strong and aesthetic. Like a - secure program, secure walls depend on sturdy bricks, solid construction, and elegant - and principled design.

      -

    3. Can I include Splint in my software distribution?

      -

      Yes. Splint is licensed under the GNU General Public License. You may redistribute - it as you wish so long as credits and pointers to www.splint.org are not changed or removed. Splint - may be included in commercial distributions, and is included in several Linux and - freeware CDs. If you redistribute Splint, please let us know by sending a message to - splint@cs.virginia.edu.

      -

    4. Can we use your software in our company? (We are not a GNU organization.)

      -

      Yes, splint is GPL-licensed. Anyone may use it. If you want to - redistribute it, check the license for details or contact us.

      -

    5. Does Splint handle C++?

      -

      No. Splint handles ISO C99 (and some gcc extensions if +gnuextensions is used). We - don't have the resources (or the research justification) to build a C++ front end, - but if you are interested in building a C++ front end the source code is available, - and I will certainly be willing to help.

      -

    6. I downloaded the Splint .tgz file but can't figure out how to extract it. There is - no 'z' option on the tar on my system.

      -

      Check to see if there is GNU tar on your system, it is usually invoked by the - command gtar or gnutar. GNU tar supports the -z option.

      -

      You can also unzip the file then untar it. Do: gunzip filename.tar.gz to unzip - then tar -xvf filename.tar

      -

    7. I want to use Splint in win2000. How do I do that?

      -

      See www.splint.org for information on - Splint.

      -

      http://www.splint.org/win32.html - for Windows instructions.

      -

    8. I have installed Splint for Windows 2000. Where should I put the ".splintrc" - file?

      -

      For Win32, Splint looks for splint.rc instead of .splintrc due to the DOS filename problems. It will look first in the current directory, then in

      -

      your home directory. See the Splint manual for more information.

      -
      -

    9. Which compilers does Splint support?

      -

      It is independent from your compiler.

      -

    10. How does Splint handle const?

      -

      Splint doesn't interpret const (at all). See the manual section on - modifies checking (http://www.splint.org/manual/html/sec7.html).

      -

    11. Why do I get a Warning when multiplying different integer types? The C standard - says this is ok. Why is this wrong?

      -

      There are lots of things that the C spec allows and defines clearly, that Splint will provide warnings for. It's not a question of it being "wrong", - it's a matter of it being likely to reveal a programming mistake.

      -

    12. The C standard says that what I'm doing is okay. Why does Splint give me a - warning?

      -

      See the previous question.

      -

    13. Splint complains if I ignore the return value of scanf but not printf?

      -

      This is just a strategic decision --- we view ignoring the result of a - scanf to be more likely to reveal a problem with the code than ignoring - the result of a printf, even though strict programmers will want to check - printf also.

      -

      If you want stricter checking, use the flags +ansistrictlib, +posixstrictlib, - +unixstrictlib to select the strict versions of these libraries.

      -
      -

    14. I develop code on an embedded system with a compiler that uses nonstandard key - words and data types. I would like to run Splint on my code but these nonstandard - keywords cause parse errors. What should I do?

      +

      General Questions About Splint

      +
    15. +

      What is the difference between Splint and + LCLint?

      +

      Before 2002, Splint was known as LCLint. Splint 3.0 is the successor to LCLint + 2.5.

      +
      + LCLint was originally named for LCL, the Larch C Interface Language and lint, a + well-known C program checking tool. Because our tool has diverged from LCL, and + our focus now is on secure programming, it was renamed Splint. Splint's name + has (at least) three interpretations: specifications lint, secure programming + lint, and first aid for programmers. It's also easier to pronounce than + LCLint.
      +
      +
      +
      16. +
    16. +

      What is the Splint logo?

      +
      + Thomas Jefferson's Serpentine Walls at the University of Virginia. The walls + are one brick thick, but because of their design are both strong and aesthetic. + Like a secure program, secure walls depend on sturdy bricks, solid + construction, and elegant and principled design.
      +
      +
      +
      17. +
    17. +

      Can I include Splint in my software + distribution?

      +
      + Yes. Splint is licensed under the GNU General Public License. You may + redistribute it as you wish so long as credits and pointers to www.splint.org are not changed or removed. + Splint may be included in commercial distributions, and is included in several + Linux and freeware CDs. If you redistribute Splint, please let us know by + sending a message to splint@cs.virginia.edu.
      +
      +
      +
      18. +
    18. +

      Can we use your software in our company? (We are + not a GNU organization.)

      +
      + Yes, splint is GPL-licensed. Anyone may use it. If you want to redistribute it, + check the license for details or contact us.
      +
      +
      +
      19. -

      You can often use -D to solve this problem.

      -

      If you just want to ignore a keyword, you can add - -Dnonstandardkeyword= - to make the preprocessor eliminate the keyword, where nonstandardkeyword is the - name of the keyword. Similarly, you can use - -Dspecialtype=int - to make a custom type parse as an int.

      -

    19. How can I get Splint to recognize directory trees and local source include - directories? I've tried putting them in my path but it doesn't seem to look beyond - the current directory.

      -

      You can use -I to set the include path like you would with a compiler.

      -

    20. I heard that we will get lot of parse errors when we run this tool first time. - Hence we need to modify source code. Is it correct ?

      -

      Usually not, but Splint doesn't support all C99 extensions.

      -

    21. I heard that Splint can generate some spurious errors ( not genuine errors). Is it - correct ?

      -

      Yes, please see www.splint.org for - details.

      -

    22. When I build Splint I get the following error:

      -

      Checking for...

      -

      Checking manual...

      -

      cmx > / Checking tests2.2...

      -

      Checking tests2.4...

      -

      Checking tests2.5...

      -

      Checking db1...

      -

      0a1,2

      -

      > /cmx/tools/make -e clean

      -

      > /cmx/tools/make -e check

      -

      *** FAIL ***

      -

      Checking db2...

      -

      0a1,/tools/make -e clean

      -

      > /cmx/tools/make -e check

      -

      *** FAIL ***

      -

      Checking db3...

      -
      -

      Should I be worried?

      - -

      Those diffs look harmless. It is likely that your make is set up slightly - differently than ours.

      -

    23. I just installed Splint on a new machine. I get a bunch of errors during building - when the test suite is run. When I look through the results, it seems like Splint is - not reporting any errors in the code it analyzes. What is going on?

      -

      One possibility is that the installation directory where the test suite is - running is on the system path (hence, splint won't report errors if - -sysdirerrors is set, as it is by default). Try adding +sysdirerrors to - the command line for the test suite to see if that is the problem, or installing - Splint in a different directory not in the system path.

      -

    24. I get parse errors when I try to run Splint on code like #define MACROdebug(...) - blahblah . Can I use variadic macros in Splint?

      -

      Sorry, Splint does not yet support variadic macros. We hope to fix this in a - future release.

      -

    25. I use realloc in my code. How can I get Splint in check this code more - effectively?

      -

      realloc has complicated semantics that make it difficult to use correctly. Make - sure that you understand realloc and that you really need to use it.

      -

      If you decide to use realloc, we recommend that you wrapper it. The document Using - Wrapper Functions explains how to do this. That document is included in the Splint - documentation and is also available at:

      -

      http://www.splint.org/documentation/realloc.htm

      -

    26. I think I've found a bug in Splint. What should I do?

      -

      See http://www.splint.org/bugs.html - for a list of known bugs and instructions on reporting bugs.

      -

    27. Splint tells me that there is a bug and I should report it. What information - should I send?

      -

      Ideally we would like enough code to reproduce the problem. Small snippets of code - which trigger the bug are the best but more code is also acceptable.

      -

      If we're not able to reproduce the problem, then we are unlikely to be able to - patch Splint. However, we would still appreciate hearing about the bug and may be - able to at least to offer you advice on working around the problem.

      -

    28. My question isn't answered here. How can I get more information about Splint?

      -

      First check the Splint manual and the mailing list archives.

      -

      The Splint manual is available at: http://www.splint.org/manual/

      -

      The mailing list archives are at:

      -

      http://www.mail-archive.com/lclint-interest%40virginia.edu/

      -

      If you're still unable to find the information to answer your question, you can - try posting the question to the splint-discuss mailing list (see http://www.splint.org/lists.html)

      -

      You can also email us at splint@splint.org.

      -
      - +
    29. +

      Which compilers does Splint support?

      +
      + It is independent from your compiler.
      +
      +
      +
      30. - - - - - - +
    30. +

      Does Splint handle C++?

      +
      + No. Splint handles ISO C99 (and some gcc extensions if +gnuextensions is used). + We don't have the resources (or the research justification) to build a C++ + front end, but if you are interested in building a C++ front end the source + code is available, and I will certainly be willing to help.
      +
      +
      +
      31. +
    31. +

      I downloaded the Splint .tgz file but can't + figure out how to extract it. There is no 'z' option on the tar on my + system.

      +
      + Check to see if there is GNU tar on your system, it is usually invoked by the + command gtar or gnutar. GNU tar supports the -z option.
      +
      + +

      You can also unzip the file then untar it. Do: gunzip filename.tar.gz to + unzip then tar -xvf filename.tar

      +
      +
      32. +
    32. +

      I want to use Splint in win2000. How do I do + that?

      +
      + See www.splint.org for information on + Splint.
      +
      + +

      http://www.splint.org/win32.html + for Windows instructions.

      +
      +
      33. +
    33. +

      I have installed Splint for Windows 2000. Where + should I put the ".splintrc" file?

      +
      + For Win32, Splint looks for splint.rc instead of .splintrc due to the DOS + filename problems. It will look first in the current directory, then in
      +
      + +

      your home directory. See the Splint manual for more information.

      +
      +
      34. +

      Usage

      - - - - - -
      - - - - - - - - - - - - - - - - - -
      -Splint - Secure Programming Lint - - - -info@splint.org - -
      - -Download -- -Documentation - -- -Manual -- -Links
      - -Source -- -Linux -- -Publications -- -Talks
      - -       - -      		 - - -Reporting -Bugs - -Mailing -Lists    - -   -Sponsors - -- -Credits - -
      - -
      - +
    34. +

      How does Splint handle const?

      +
      + Splint doesn't interpret const (at all). See the manual section on modifies + checking (http://www.splint.org/manual/html/sec7.html).
      +
      +
      +
      35. +
    35. +

      Why do I get a Warning when multiplying + different integer types? The C standard says this is ok. Why is this + wrong?

      +
      + There are lots of things that the C spec allows and defines clearly, that + Splint will provide warnings for. It's not a question of it being "wrong", it's + a matter of it being likely to reveal a programming mistake.
      +
      +
      +
      36. +
    36. +

      The C standard says that what I'm doing is + okay. Why does Splint give me a warning?

      +
      + See the previous question.
      +
      +
      +
      37. +
    37. +

      Splint complains if I ignore the return value + of scanf but not printf?

      +
      + This is just a strategic decision --- we view ignoring the result of a scanf to + be more likely to reveal a problem with the code than ignoring the result of a + printf, even though strict programmers will want to check printf also.
      +
      + +
      + If you want stricter checking, use the flags +ansistrictlib, +posixstrictlib, + +unixstrictlib to select the strict versions of these libraries.
      +
      +
      +
      +
      38. +
    38. +

      I develop code on an embedded system with a + compiler that uses nonstandard key words and data types. I would like to run + Splint on my code but these nonstandard keywords cause parse errors. What should + I do?

      +
      +

      You can often use -D to solve this problem.

      +

      If you just want to ignore a keyword, you can add -Dnonstandardkeyword= to + make the preprocessor eliminate the keyword, where nonstandardkeyword is the + name of the keyword. Similarly, you can use -Dspecialtype=int to make a custom + type parse as an int.

      +
      +
      39. +
    39. +

      How can I get Splint to recognize directory + trees and local source include directories? I've tried putting them in my path + but it doesn't seem to look beyond the current directory.

      +
      + You can use -I to set the include path like you would with a compiler.
      +
      +
      +
      40. +
    40. +

      I heard that we will get lot of parse errors + when we run this tool first time. Hence we need to modify source code. Is it + correct ?

      +
      + Usually not, but Splint doesn't support all C99 extensions.
      +
      +
      +
      41. +
    41. +

      I heard that Splint can generate some spurious + errors ( not genuine errors). Is it correct ?

      +
      + Yes, please see www.splint.org for + details.
      +
      +
      +
      42. +
    42. +

      When I build Splint I get the following + error:

      +
      + Checking for...
      +
      + +

      Checking manual...

      +

      cmx > / Checking tests2.2...

      +

      Checking tests2.4...

      +

      Checking tests2.5...

      +

      Checking db1...

      +

      0a1,2

      +

      > /cmx/tools/make -e clean

      +

      > /cmx/tools/make -e check

      +

      *** FAIL ***

      +

      Checking db2...

      +

      0a1,/tools/make -e clean

      +

      > /cmx/tools/make -e check

      +

      *** FAIL ***

      +

      Checking db3...

      +
      +

      Should I be worried?

      +
      + Those diffs look harmless. It is likely that your make is set up slightly + differently than ours.
      +
      +
      +
      43. +
    43. +

      I just installed Splint on a new machine. I get + a bunch of errors during building when the test suite is run. When I look through + the results, it seems like Splint is not reporting any errors in the code it + analyzes. What is going on?

      +
      + One possibility is that the installation directory where the test suite is + running is on the system path (hence, splint won't report errors if + -sysdirerrors is set, as it is by default). Try adding +sysdirerrors to the + command line for the test suite to see if that is the problem, or installing + Splint in a different directory not in the system path.
      +
      +
      +
      44. +
    44. +

      I get parse errors when I try to run Splint + on code like #define MACROdebug(...) blahblah . Can I use variadic macros in + Splint?

      +
      + Sorry, Splint does not yet support variadic macros. We hope to fix this in a + future release.
      +
      +
      +
      45. +
    45. +

      I use realloc in my code. How can I get Splint + in check this code more effectively?

      +
      + realloc has complicated semantics that make it difficult to use correctly. Make + sure that you understand realloc and that you really need to use it.
      +
      + +

      If you decide to use realloc, we recommend that you wrapper it. The document + Using Wrapper Functions explains how to do this. That document is included in + the Splint documentation and is also available at:

      +

      http://www.splint.org/documentation/realloc.htm

      +
      +
      46. +
    46. +

      I think I've found a bug in Splint. What should + I do?

      +
      + See http://www.splint.org/bugs.html for + a list of known bugs and instructions on reporting bugs.
      +
      +
      +
      47. +
    47. +

      Splint tells me that there is a bug and I + should report it. What information should I send?

      +
      + Ideally we would like enough code to reproduce the problem. Small snippets of + code which trigger the bug are the best but more code is also acceptable.
      +
      + +

      If we're not able to reproduce the problem, then we are unlikely to be able + to patch Splint. However, we would still appreciate hearing about the bug and + may be able to at least to offer you advice on working around the problem.

      +
      +
      48. +
    48. +

      My question isn't answered here. How can I get + more information about Splint?

      +
      + First check the Splint manual and the mailing list archives.
      +
      + +

      The Splint manual is available at: http://www.splint.org/manual/

      +

      The mailing list archives are at:

      +

      http://www.mail-archive.com/lclint-interest%40virginia.edu/

      +

      If you're still unable to find the information to answer your question, you + can try posting the question to the splint-discuss mailing list (see http://www.splint.org/lists.html)

      +

      You can also email us at splint@splint.org.

      +
      +
      49. +
    + diff --git a/src/Makefile.am b/src/Makefile.am index 317310d..bc16e65 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -141,7 +141,7 @@ HEADERSRC = Headers/abstBodyNode.h Headers/ltokenList.h \ Headers/declaratorInvNodeList.h Headers/pairNodeList.h \ Headers/declaratorNode.h Headers/paramNode.h \ Headers/declaratorNodeList.h Headers/paramNodeList.h \ - Headers/dmalloc.h Headers/portab.h \ + Headers/dmalloc.h Headers/osd.h \ Headers/ekind.h Headers/pp.h \ Headers/enumNameList.h Headers/privateNode.h \ Headers/enumNameSList.h Headers/programNode.h \ @@ -229,6 +229,7 @@ HEADERSRC = Headers/abstBodyNode.h Headers/ltokenList.h \ Headers/lsymbolList.h Headers/warnClause.h \ Headers/lsymbolSet.h Headers/ynm.h \ Headers/ltoken.h Headers/splintMacros.nf \ + Headers/typeId.h \ Headers/pointers.h Headers/mstring.h Headers/help.h diff --git a/src/Makefile.in b/src/Makefile.in index a7663b8..af506c8 100644 --- a/src/Makefile.in +++ b/src/Makefile.in @@ -237,7 +237,7 @@ HEADERSRC = Headers/abstBodyNode.h Headers/ltokenList.h \ Headers/declaratorInvNodeList.h Headers/pairNodeList.h \ Headers/declaratorNode.h Headers/paramNode.h \ Headers/declaratorNodeList.h Headers/paramNodeList.h \ - Headers/dmalloc.h Headers/portab.h \ + Headers/dmalloc.h Headers/osd.h \ Headers/ekind.h Headers/pp.h \ Headers/enumNameList.h Headers/privateNode.h \ Headers/enumNameSList.h Headers/programNode.h \ @@ -325,6 +325,7 @@ HEADERSRC = Headers/abstBodyNode.h Headers/ltokenList.h \ Headers/lsymbolList.h Headers/warnClause.h \ Headers/lsymbolSet.h Headers/ynm.h \ Headers/ltoken.h Headers/splintMacros.nf \ + Headers/typeId.h \ Headers/pointers.h Headers/mstring.h Headers/help.h diff --git a/test/Makefile.am b/test/Makefile.am index 903b074..6331482 100644 --- a/test/Makefile.am +++ b/test/Makefile.am @@ -1016,6 +1016,9 @@ EXTRA_DIST = ./abst_t.lcl \ ./db3/erc.lcl \ ./db3/eref.lcl \ ./db3/ereftab.lcl \ + ./db3/README \ + ./db3/clean \ + ./db3/tidy \ ./tq.lcl \ ./ud2.lcl \ ./for/.splintrc \ diff --git a/test/Makefile.in b/test/Makefile.in index 930d2b5..55d5b67 100644 --- a/test/Makefile.in +++ b/test/Makefile.in @@ -240,6 +240,9 @@ EXTRA_DIST = ./abst_t.lcl \ ./db3/erc.lcl \ ./db3/eref.lcl \ ./db3/ereftab.lcl \ + ./db3/README \ + ./db3/clean \ + ./db3/tidy \ ./tq.lcl \ ./ud2.lcl \ ./for/.splintrc \ diff --git a/test/db3/bool.lcl b/test/db3/bool.lcl index 667508e..642b786 100644 --- a/test/db3/bool.lcl +++ b/test/db3/bool.lcl @@ -1,7 +1,9 @@ -immutable type bool; +/*immutable type bool; + constant bool TRUE; constant bool FALSE; +*/ void bool_initMod (void) internalState; { modifies internalState; } observer char *bool_unparse (bool b) { modifies nothing; }