Write once, compile anywhere

<h2 id="introduction">Introduction</h2>
<p>There are many languages that aim to allow developers to follow the WOCA philosophy, such as <a href="/facts/C%252B%252B/Et0F2qn9">C++</a>, <a href="/facts/Pascal_programming_language/b3yvp8bF">Pascal</a> (see <a href="/facts/Free_Pascal/kmGChqAg">Free Pascal</a>), <a href="/facts/Ada_programming_language/Y2yHel4l">Ada</a>, <a href="/facts/Cobol/wVnhqs0k">Cobol</a>, or <a href="/facts/C_(programming_language)/Ky2No763">C</a>, on condition that they don't use functions beyond those provided by the <a href="/facts/Standard_library/g9QS3vy0">standard library</a>. Languages like <a href="/facts/Go_(programming_language)/oWlsmAFJ">Go</a> go even further in as far that no system specific things are used, it should just work, and for system-specific elements a system of platform-specific files is used. A computer program may also use cross-platform libraries, which provide an <a href="/facts/Abstraction_layer/EV8c84SY">abstraction layer</a> hiding the differences between various platforms, for things like <a href="/facts/Internet_socket/r1ldfkb5">sockets</a> and <a href="/facts/Graphical_user_interface/wBlQFWDP">GUI</a>, ensuring the portability of the written source code. This is, for example, supported by <a href="/facts/Qt_(software)/gVhwlQnJ">Qt</a> (C++) or the <a href="/facts/Lazarus_(IDE)/6Il32HeV">Lazarus</a> (Pascal) IDE via its <a href="/facts/Lazarus_Component_Library/LhrHNzxy">LCL</a> and corresponding <a href="/facts/Widgetset/daVw6Dr5">widgetsets</a>.
</p><p>Today, we have very powerful desktop computers as well as computers in our phones, which often have sophisticated applications such as <a href="/facts/Word_processing/qAR7lagF">word processing</a>, <a href="/facts/Database_management/VYcpkevb">Database management</a>, and <a href="/facts/Spreadsheet/0cvc1GeB">spreadsheets</a>, that can allow people with no programming experience to, sort, extract, and manipulate their data. and create documents (such as <a href="/facts/PDF/C9Mn1vYL">PDF</a> files) showing their now organized information, or printing it out. Before 2000, some of these were not available, and prior to 1980, almost none of them were.
</p><p>From the start of <a href="/facts/Computer_Automation/GkMy8I4W">computer automation</a> in the early 1960s, if you wanted a report from data you had, or needed to print up <a href="/facts/Invoice/Ad1XP7qp">invoices</a>, payroll checks, <a href="/facts/Purchase_order/caBsYrlP">purchase orders</a>, and other paperwork businesses, schools and governments generated, you typed them up on a physical typewriter, possibly using pre-printed forms. Otherwise, if you did have information stored in a computer, and wanted it sorted, manipulated, or printed, it required someone to write a program to do so. In some cases, the person needed information that professional programmers either could not understand how to provide a program to do what they wanted; the available programmers could not produce something in a reasonable amount of time; or there weren't any programmers they could use, caused some non-programming professionals to learn some programming skills, at least to know how to manipulate and print out information they needed from their data.
</p><p>Whether the work was done by a professional programmer, or an <a href="/facts/End-user/7IM9qu7N">end-user</a> writing a program to provide them information for their own use, the means to do this in either case is the same. Write a program, submit it to a <a href="/facts/Compiler/WNfCDFJe">compiler</a> (another program that converts written programs into instructions the computer can understand), fix any errors, then repeat until the program worked.
</p><p>While this helped fix part of the problem, it created a new one. People who wrote programs, or hired someone to write them (purchasing software was not a thing until the 1970s or 1980s), discovered when their employer or school bought a new computer, their programs no longer worked.
</p>
<h2 id="development-of-high-level-programming-languages">Development of high-level programming languages</h2>
<p>To combat these problems, various <a href="/facts/High-level_language/smjECUhx">high-level languages</a> were developed that were usable for general purpose application program development, but could be used to provide reports and information for people with specialized requirements.
</p><p>These include:
</p>
<ul><li><a href="/facts/BASIC/ELoTkjnM">BASIC</a>, a simplified programming language which could be used to build "real world" complex applications, as well as simple programs to solve a problem, and was very accessible for amateur programmers. Its ease of use made BASIC well suited as an introductory <a href="/facts/Computer_programming/QmSsFnu0">computer programming</a> class in many colleges.</li>
<li><a href="/facts/C_(programming_language)/Ky2No763">C</a>, a <a href="/facts/General-purpose_programming_language/LyA5zR3M">general-purpose programming language</a> often suitable for writing programs which would otherwise require <a href="/facts/Assembly_language/7XuV0cla">assembly language</a>.</li>
<li><a href="/facts/Cobol/wVnhqs0k">Cobol</a>, a general-purpose programming language which tended to be used for developing business applications.</li>
<li><a href="/facts/Fortran/m1KqjcMU">Fortran</a>, a general-purpose programming language which is well suited for scientific and engineering problems.</li>
<li><a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal</a>, a general-purpose programming language, which tended to be targeted toward use in schools as an introductory class to teach programming as an alternative to BASIC. Pascal became commonly used for hobbyist programmers in the 1970s and 1980s due to them being part of an <a href="/facts/Integrated_development_environment/jbEINSQf">integrated development environment</a> allowing a person to edit, compile, and run their programs, providing immediate results. Programs such as <a href="/facts/UCSD_Pascal/xxmwFYV5">UCSD Pascal</a> and <a href="/facts/Turbo_Pascal/2aWFEk9z">Turbo Pascal</a> opened up the world of programming to millions of people,</li>
<li><a href="/facts/IBM_RPG_III/F1wLYRxc">RPG</a>, a <a href="/facts/Domain-specific_programming_language/n18H1foD">domain-specific programming language</a> designed to take the contents of data files, manipulate data and do calculations, then produce printed reports, similar to the way a person can use a spreadsheet to organize data and create <a href="/facts/PDF/C9Mn1vYL">PDF</a> files today.</li></ul>
<p>While <a href="/facts/Compiler/WNfCDFJe">compilers</a> and <a href="/facts/Interpreter_(computing)/JB85fbyb">interpreters</a> of all of these languages, and dozens of others, were available for different machines and different vendors, often each manufacturer would develop proprietary enhancements which made programing on that machine easier, but again, made programs difficult to port (move the program to a different type of computer or a different vendor's computers), and increased vendor lock in. Something had to change.
</p>
<h2 id="standardization">Standardization</h2>
<p>Starting in the late 1960s and early 1970s, efforts came into play to create standards and specifications of how machine-independent programs could be written using compilers from any vendor. Standards-making organizations, like the <a href="/facts/International_Standards_Organization/IacYR7Yg">International Standards Organization</a> (ISO), and <a href="/facts/ANSI/EzhCdC3s">ANSI</a>, among others, in cooperation with large users of computers and software (like governments, financial institutions and manufacturers), and computer manufacturers, to create standardized specifications to provide a description of how each specific language should be implemented.
</p><p>Computer manufacturers could still have their own proprietary extensions to a programming language, but if they wanted to be able to claim compliance with the standard, they had to specify the differences in the reference manual, so that a program written according to the standard able to compile and operate on their machine would also operate, without further change, on a different manufacturer's computer whose compiler also followed the standard. The requirements of the standard were enforced by large software buyers, such as military, government, and manufacturing companies, by refusing to buy such computing equipment if the vendor only offered a compiler for the programming languages they used which wasn't compliant with the standard.
</p>
<h2 id="results">Results</h2>
<p>Currently, there are more than a dozen programming languages that have standards describing how programs in the language are supposed to be written, including <a href="/facts/Ada_(programming_language)/Y2yHel4l">Ada</a>, <a href="/facts/APL_(programming_language)/E2sb98gC">APL</a>, <a href="/facts/BASIC/ELoTkjnM">BASIC</a>, <a href="/facts/C%252B%252B/Et0F2qn9">C++</a>, <a href="/facts/COBOL/wVnhqs0k">COBOL</a>, <a href="/facts/ECMAScript/M7nDHsB5">ECMAScript</a> (the generic name for <a href="/facts/JavaScript/XhhIIEsl">JavaScript</a>), <a href="/facts/Forth_(programming_language)/mYtWVNhF">Forth</a>, <a href="/facts/FORTRAN/m1KqjcMU">FORTRAN</a>, <a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal</a>, <a href="/facts/PL%2fI/469mVYgd">PL/I</a>, <a href="/facts/Ruby_(programming_language)/BeYSaPSR">Ruby</a> and <a href="/facts/SQL/UjQLJcYm">SQL</a>. Many of these are still in use, in some cases, because customers were able to take their source code to a different manufacturer's computer, where it was recompiled, often without change, because of the standardization of programming languages.
</p><p>While the standards helped, the WOCA philosophy works only when the makers of compilers ensure that they follow the standard.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Pivot_language/Pr0JWgzB">Pivot language</a></li></ul>

Write once, compile anywhere open-in-new

Write once, compile anywhere