Programming tool: Difference between revisions
write an article |
No edit summary |
||
| Line 1: | Line 1: | ||
A '''programming tool''' is a [[software application]] that can be used |
A '''programming tool''' is a [[computer program|program]] or [[software application]] that [[software developer]]s use to help create, debug, or maintain other programs and applications. The term usually refers to relatively simple programs that can be used together to accomplish a task, much as one might use multiple hand [[tool]]s to fix a physical object. |
||
The history of software tools began with the first computers in the early 1950s that used linkers, loaders, and control programs. Tools became famous with Unix in the early 1970s with tools like [[grep]], [[awk]] and [[make]] that where meant to be combined flexibly with [[pipe (computing)|pipe]]s. |
|||
| ⚫ | |||
Tools were originally simple and light weight. As some tools have been maintained, they have |
|||
been integrated into more powerful [[integrated development environment]]s (IDEs). |
|||
These environments can make searching and editing much easier, however they lack the |
|||
ability to massage code, like old Unix tools. |
|||
The distinction between tools and applications can become murky. For example, developers use simple |
|||
databases (such as a file containing list of important values) all the time as tools. |
|||
However a full blown database is usually thought of as much more than a tool. |
|||
The ability to use a variety of tools productively is one hallmark of a skilled software engineer. |
|||
== List of tools == |
|||
Software tools come in many forms: |
|||
* Source Code Control: [[SCCS]], [[RCS]], [[CVS]], [[SourceSafe]], [[PVCS]], [[ClearCase]] |
|||
* Compilation and linking tools: [[Make]], [[automake]] |
|||
* Search: [[grep]], [[find]] |
|||
* Editors: [[emacs]], [[vi]] |
|||
* Scripts: [[Shell]], [[Perl]] |
|||
* Parsing: [[Lex]], [[Yacc]] |
|||
* Bug Databases: [[gnats]], [[Bugzilla]] |
|||
[[Debugging]] tools also are used in the process of debugging code, and can also be used to create code that is more compliant to standards and portable than if they were not used. In the [[C programming language]] for instance, [[memory leak]]s are not as easily detected - software tools are often used to find memory leaks enabling the programmer to find these problems much more efficiently than sight alone. |
[[Debugging]] tools also are used in the process of debugging code, and can also be used to create code that is more compliant to standards and portable than if they were not used. In the [[C programming language]] for instance, [[memory leak]]s are not as easily detected - software tools are often used to find memory leaks enabling the programmer to find these problems much more efficiently than sight alone. |
||
See also: |
|||
== List of IDEs == |
|||
[[Integrated development environments]] (IDEs) combine the features of many tools, |
|||
into one complete package. They are usually simpler and easier to do simple |
|||
tasks, such as seaching for content only in files in the project. They usually |
|||
have a much harder time with linking tools together, such as preprocessors and code generators. |
|||
| ⚫ | Integrated development environments are often used for development of enterprise-level applications, especially on [[Microsoft Windows]] based machines, however IDEs (as they are also known) also exist on other operating systems. [[IBM]]'s [[VisualAge]] development tools run on [[OS/2]], for instance. |
||
* [[Visual studio]] |
|||
* [[JBuilder]] |
|||
* [[Visual age]] |
|||
== See Also == |
|||
* [[Software engineering]] |
|||
* [[Computer science]] |
|||
* [[Aard]] |
* [[Aard]] |
||
* [[Bonsai CVS code management system]] |
* [[Bonsai CVS code management system]] |
||
Revision as of 23:48, 16 February 2004
A programming tool is a program or software application that software developers use to help create, debug, or maintain other programs and applications. The term usually refers to relatively simple programs that can be used together to accomplish a task, much as one might use multiple hand tools to fix a physical object.
The history of software tools began with the first computers in the early 1950s that used linkers, loaders, and control programs. Tools became famous with Unix in the early 1970s with tools like grep, awk and make that where meant to be combined flexibly with pipes.
Tools were originally simple and light weight. As some tools have been maintained, they have been integrated into more powerful integrated development environments (IDEs). These environments can make searching and editing much easier, however they lack the ability to massage code, like old Unix tools.
The distinction between tools and applications can become murky. For example, developers use simple databases (such as a file containing list of important values) all the time as tools. However a full blown database is usually thought of as much more than a tool.
The ability to use a variety of tools productively is one hallmark of a skilled software engineer.
List of tools
Software tools come in many forms:
- Source Code Control: SCCS, RCS, CVS, SourceSafe, PVCS, ClearCase
- Compilation and linking tools: Make, automake
- Search: grep, find
- Editors: emacs, vi
- Scripts: Shell, Perl
- Parsing: Lex, Yacc
- Bug Databases: gnats, Bugzilla
Debugging tools also are used in the process of debugging code, and can also be used to create code that is more compliant to standards and portable than if they were not used. In the C programming language for instance, memory leaks are not as easily detected - software tools are often used to find memory leaks enabling the programmer to find these problems much more efficiently than sight alone.
List of IDEs
Integrated development environments (IDEs) combine the features of many tools, into one complete package. They are usually simpler and easier to do simple tasks, such as seaching for content only in files in the project. They usually have a much harder time with linking tools together, such as preprocessors and code generators.
Integrated development environments are often used for development of enterprise-level applications, especially on Microsoft Windows based machines, however IDEs (as they are also known) also exist on other operating systems. IBM's VisualAge development tools run on OS/2, for instance.