
	Where results make sense

Topic: Lint programming tool

Related Topics

Software development tools

Artificial intelligence

In the News (Mon 6 Jul 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Lint programming tool
		Lint was a programming tool that first appeared (outside of Bell Labs) in the seventh version (V7) of the UNIX operating system in 1979.
		Lint performed the lexical and syntatic portions of the compilation with substantial additional checks, noting when variables had been used before being set, when they were used as a datatype other than that of their definition, and numerous other programming errors.
		The name of the program was derived from the notion that it would lead to "cleaner", more desirable programming, by picking the "lint" -- little bits of fluff -- out of one's code.
	www.ebroadcast.com.au /lookup/encyclopedia/li/Lint_programming_tool.html (176 words)

	Tool
		Although tools were once thought to be used only by humans, it has been observed that chimpanzees and other animals, mostly primates, but also for instance ravens, are able to use them as well.
		An instrument is a concrete or abstract tool, in particular a refined one.
		Tool can also refer to a person who is being manipulated by someone else, in a similar sense as puppet.
	www.ebroadcast.com.au /lookup/encyclopedia/to/Tool.html (291 words)

	Lint
		Lint is a municipality located in the Belgian province of Antwerp.
		On January 1st, 2000 Lint had a total population of 7,864 (3,883 males and 3,981 females).
		Lint, also known colloquially as flooze, is a material composed of loosely compressed clothing fibers which accumulates in the pockets of clothes and in the filters of washing machines.
	www.guajara.com /wiki/en/wikipedia/l/li/lint.html (113 words)

	News \| Gainesville.com \| The Gainesville Sun \| Gainesville, Fla. (Site not responding. Last check: 2007-10-11)
		Lint was the original name given to a particular tool that flagged suspicious and non-portable constructs (ie, likely to be bugs) in C language source code.
		Many of the forms of analysis performed by Lint-like tools are also performed by optimizing compilers (whose prime motivation is to generate higher quality code), and such compilers are also starting to support the detection of many of the constructs traditionally warned about by Lint.
		Modern tools (see List of tools for static code analysis) perform forms of analysis that many optimizing compilers typically don't do, such as cross-module consistency checking, checking that the code will be portable to other compilers, and support for annotations to specify the intended behavior or properties of code.
	www.gainesville.com /apps/pbcs.dll/section?category=NEWS&template=wiki&text=lint_programming_tool (314 words)

	Lint programming tool Article, Lintprogrammingtool Information (Site not responding. Last check: 2007-10-11)
		Lint is a computer programming tool thatperforms the lexical and syntactic portions of the compilation with substantial additional checks, noting when variables had beenused before being set, when they were used as a datatype other than that of their definition, and numerous other programmingerrors.
		The name of the program was derived from the notion that it would lead to "cleaner", more desirable programming, by pickingthe "lint" -- little bits of fluff -- out of one's code.
		Lint also does some kinds of analysis that compilers typically don't do, such as cross-module consistency checking, andchecking that the code will be portable to other compilers.
	www.anoca.org /compiler/compilers/lint_programming_tool.html (255 words)

	PDC's Tutorial on LINT
		LINT detects parts of a program that cannot be reached during execution.
		LINT also detects certain kinds of infinite loops as well as loops that cannot be exited or entered.
		LINT also detects type casts, which are legal C language constructs that allow the program to treat data of one type as if it were data of another type.
	www.pdc.kth.se /training/Tutor/Basics/lint/index-frame.html (919 words)

	Embedded.com - Introduction to Lint
		Lint is a tool similar to a compiler in that it parses C/C++ source files.
		Lint is designed to be compiler-agnostic and is, in fact, frequently in the business of focusing your attention on parts of the code that might result in different behavior depending on the specific compiler used.
		Lint checks so many things, in fact, that it's usual for the tool to produce as many errors and warnings as there are lines of code in the source file that's input.
	www.embedded.com /story/OEG20020429S0033 (1329 words)

	Linux.com - Tools
		One obvious type of tool is a program to examine the source code to search for patterns of known potential security problems (e.g., calls to library functions in ways are often the source of security vulnerabilities).
		The programmer annotates their program in a few places, and cqual performs qualifier inference to check whether the annotations are correct.
		These kinds of tools are very useful for doing regression testing, but since they essentially use a list of past specific vulnerabilities and common configuration errors, they may not be very helpful in finding problems in new programs.
	www.linux.com /howtos/Secure-Programs-HOWTO/tools.shtml (1176 words)

	oreilly.com -- Online Catalog: Checking C Programs with Lint
		The lint program is one of the best tools for finding portability problems and certain types of coding errors in C programs.
		The lint program checker has proven time and again to be one of the best tools for finding portability problems and certain types of coding errors in C programs.
		lint verifies a program or program segments against standard libraries, checks the code for common portability errors, and tests the programming against some tried and true guidelines.
	www.oreilly.com /catalog/lint (344 words)

	Programming Tools Tutorial Notes
		The programs lint and alint check C programs for portability problems, syntax errors, wasteful style, and other forms of bugs; lint understands traditional C while alint is for ANSI C. Lint is extremely thorough and perfectly capable of making even the best programmer look bad.
		Note also that programs that have been "stripped", either with the -s option at link-time or the "strip" program, have no namelist or symbol table, and therefore cannot be debugged.
		The "profile" of a program is a breakdown of the program's execution, showing the amount of calls or the amount of time spent on any particular activity.
	www.seas.rochester.edu /CNG/docs/ProgTools.html (3830 words)

	Static Analysis Tools for C Code
		This tool is focused primarily on the detection of memory leaks, and not on general source code analysis.
		There is a plan to extend the tool with a rule checker for strong set of coding rules for safety critical code, which will make it attractive for high integrity applications.
		Astree is a static program analyzer for structured C programs, but without support for dynamic memory allocation and recursion (as used, for instance for embedded systems and in safety critical systems).
	www.spinroot.com /static (769 words)

	Splint Manual
		Splint is the successor to LCLint, a tool originally developed as a joint research project between the Massachusetts Institute of Technology and Digital Equipment Corporation’s System Research Center.
		Some annotations, known as control comments, may appear between any two tokens in a C program (unlike regular C comments, control comments should not be used within a single token as they introduce new separators in the code).
		When checking unannotated programs, many spurious use before definition errors may be reported If impouts is on, no error is reported when an incompletely-defined parameter is passed to a formal parameter with no definition annotation, and the actual parameter is assumed to be defined after the call.
	lclint.cs.virginia.edu /manual/manual.html (4582 words)

	Useful tools in unix (Site not responding. Last check: 2007-10-11)
		Program for converting image files from one format to another (e.g., PS to JPEG).
		A tool for "profiling" a program, to find the bottlenecks that you may wish to re-write.
		Tool for putting a set of files or directories into a single file.
	www.biostat.jhsph.edu /~kbroman/unix_tools (506 words)

	Better Software Magazine: In this Issue Featured Articles.
		Automated code analysis is an umbrella term that describes a family of software utilities and tools designed to help programmers discover, diagnose, and prevent a broad range of errors and undesirable behaviors in their code.
		However, the usefulness of Lint was in those days somewhat limited by the fact that running it was part of a rather lengthy and not very interactive edit-save-analyze cycle.
		Imagine a dynamic performance analysis tool that takes a version of the code, along with a representative set of sample inputs or tests, and analyzes it to identify parameters that might affect performance (for example,the buffer size in a file read operation).
	www.stickyminds.com /bettersoftware/magazine.asp?fn=cifea (3069 words)

	Gimpel Software Home Page for PC-lint and FlexeLint for C/C++
		Visual Lint is an add-on software product which allows you to more effectively run PC-lint from within Microsoft Visual Studio and even provides for automatic background linting of your code.
		ALOA (short for A Lint Output Analyzer) is a tool that processes output generated by PC-lint and computes various useful metrics that give a quick overview of the internal quality of any C/C++ project.
		PC-lint is a tool for programmers which enables them to search for thousands of types of common errors in their game's C and C++ source code.
	www.gimpel.com (512 words)

	Killing bugs before they kill your software organization / Contents
		While 67% of software development professionals surveyed believe software tools are essential for developing quality software and 68% said they were aware of tools that could help speed development while increasing product quality, only 52% said their organizations had plans to buy such development tools.
		Toadies commercial lint tools are the progeny of a free lint utility that was released with Unix.
		While a static source code analysis tool will not eliminate the need for code reviews, compilers, debuggers, testing, or dynamic analysis, it can greatly reduce the overhead on these more expensive resources by catching problems early and allowing programmers to correct problems at the source while they are most familiar with their code.
	www.cleanscape.net /programming-solutions/code-analysis/lint_whitepaper/analysis-paper-print.html (2626 words)

	Zap bugs with PMD (Site not responding. Last check: 2007-10-11)
		Lint4j is a free (as in beer), closed source static code analysis tool that detects some of the same issues as PMD and FindBugs -- and some unique ones.
		Checkstyle is an open source code analysis tool that focuses on adherence to Java coding conventions such as line length and indentation rather than bug patterns.
		AppPerfect is a payware static code analysis tool that has the unique ability to check JSP pages as well as conventional Java source code.
	www-106.ibm.com /developerworks/library/j-pmd/index.html?ca=drs-j0305 (2138 words)

	Literate Programming - Tools
		Even if the development tools are of little to no use to you, you may have interest in the many standard Unix utilities provided with the package.
		DocJet is a tool for documenting C, C++, Java and Visual Basic programs.
		CodeSurfer is the first tool to provide precise interprocedural program slicing and pointer analysis for C programmers.
	www.literateprogramming.com /tools.html (2642 words)

	splint 1 "A tool for statically checking C programs"
		Splint is a tool for statically checking C programs for security vulnerabilities and common programming mistakes.
		Because of the provided error suppression mechanisms, these options should probably not be used for final checking real programs but may be useful in developing programs using make.
		A special reward will be presented to the first person to produce a real program that produces no errors with strict checking.
	www.math.utah.edu /~beebe/software/c-tools/splint.html (1089 words)

	Dr. Dobb's \| Lint Metrics & ALOA \| May 1, 2004
		Lint statically analyzes your source code and generates detailed lists of warnings about potential bugs, classic mistakes, and portability pitfalls.
		ALOA (short for A Lint Output Analyzer) is a tool that processes output generated by PC-lint (Gimpel Software's Lint implementation; see http://www.gimpel.com/) and computes various useful metrics that give a quick overview of the internal quality of any C/C++ project.
		It is a great tool for fine tuning the Lint policy because it shows which programming constructs/styles are typical for a project and, hence, may be suppressed globally by disabling the corresponding warnings in the Lint policy file.
	www.ddj.com /dept/cpp/184401810 (2014 words)

	Improving Your Software with Xcode and Static Code Analysis Techniques
		Static analysis tools look for dangerous programming practices, poor use of language features, or potential errors that you may have missed-in other words, problems that are just waiting to appear at the worst possible time.
		The problem was that programmers didn't use lint and instead relied on the compiler.
		Splint is a third-party lint tool that provides much better static checking than your compiler or traditional lint.
	developer.apple.com /tools/xcode/staticanalysis.html (2985 words)

	Lint traps bugs at compile time \| InfoWorld \| Analysis \| 2006-01-26 \| By Andrew Binstock
		The lint utility, which is shipped with some versions of Unix, traces its roots back to the days when compiling even modest programs took a long time.
		Lint is particularly useful for locating a bug in code that compiles correctly -- syntactically correct code that does not behave as expected almost always has an error that lint will catch.
		What lint does not do is walk every possible execution path across a large code base to find cross-functional errors.
	www.infoworld.com /article/06/01/26/74270_05FEcodelint_1.html (1210 words)

	Splint Manual - End Notes
		[1] Lint is a common programming tool for detecting anomalies in C programs.
		Johnson developed the original lint in the late seventies, mainly because early versions of C did not support function prototypes.
		To reflect divergence from LCL and increased focus on detecting security vulnerabilities, the name was changed to Splint, short for “Specification Lint” and “Secure Programming Lint”.
	www.cs.virginia.edu /~evans/lclint/manual/html/appNotes.html (659 words)

	Uno Tool Synopsis
		Static analysis tools commonly suffer from a far too low signal-to-noise ratio: they tend to produce voluminous output that consists predominantly of false alarms: instances where the analyzer cannot determine the safety of the code and throws the problem back to the programmer.
		As a small example, below is the output from the traditional Unix tool lint, from its popular recent extension lclint, and the output from Uno for a trivial C program with a single major defect (a nil-pointer derefence):
		The tool can be run also in a picky mode, where it generates the more cosmetic complaints about fall-thru on case switches, externs that could be declared static, redundant declarations etc. By default these messages are suppressed.
	spinroot.com /uno (1259 words)

	Your Lint Tool using PLI
		Ok, ok, so admittedly there are commercial Verilog lint checkers out there (which are very useful or verbose depending on your perspective).
		where the option check_name performs the lint checking for the names of the variables etc. Options can be given in any order and one, two or all three of the above checks can be done with one call to $lint_check.
		Instead it prints an error message wherever a lint voilation is found.
	www.project-veripage.com /vpilint.php (557 words)

	Compiler and tools tricks
		Use some of the commercial tools that check for memory leaks, array bounds violations, suspect code and the like.
		Step through your program when it has become clear that you have the wrong picture of how the code works.
		Furthermore, variables allocated on the stack may be optimized away in register, changing the precision and producing different results depending on the level of optimization of the program.
	www.fortran-2000.com /ArnaudRecipes/CompilerTricks.html#Lint_metrics (4276 words)

Try your search on: Qwika (all wikis)