diff options
| author | Hans Bolinder <[email protected]> | 2015-03-12 15:35:13 +0100 |
|---|---|---|
| committer | Björn Gustavsson <[email protected]> | 2015-03-12 17:42:20 +0100 |
| commit | 2d3ab68c60e8bacf9e0efe403895e7065ef683be (patch) | |
| tree | 1d2c73d661a06411fb08e81818df9e890c7271bf /system/doc/tutorial/example.xmlsrc | |
| parent | 0c20078ff0fbad9066c8dd4ebcd6faa0b4f31b42 (diff) | |
| download | otp-2d3ab68c60e8bacf9e0efe403895e7065ef683be.tar.gz otp-2d3ab68c60e8bacf9e0efe403895e7065ef683be.tar.bz2 otp-2d3ab68c60e8bacf9e0efe403895e7065ef683be.zip | |
Update Interoperability Tutorial
Language cleaned up by the technical writers xsipewe and tmanevik
from Combitech. Proofreading and corrections by Hans Bolinder.
Diffstat (limited to 'system/doc/tutorial/example.xmlsrc')
| -rw-r--r-- | system/doc/tutorial/example.xmlsrc | 21 |
1 files changed, 15 insertions, 6 deletions
diff --git a/system/doc/tutorial/example.xmlsrc b/system/doc/tutorial/example.xmlsrc index f87eb217e9..e205ca189e 100644 --- a/system/doc/tutorial/example.xmlsrc +++ b/system/doc/tutorial/example.xmlsrc @@ -4,7 +4,7 @@ <chapter> <header> <copyright> - <year>2000</year><year>2013</year> + <year>2000</year><year>2015</year> <holder>Ericsson AB. All Rights Reserved.</holder> </copyright> <legalnotice> @@ -31,16 +31,25 @@ <section> <title>Description</title> - <p>A common interoperability situation is when there exists a piece of code solving some complex problem, and we would like to incorporate this piece of code in our Erlang program. Suppose for example we have the following C functions that we would like to be able to call from Erlang.</p> - <codeinclude file="complex.c" tag="" type="none"></codeinclude> - <p>(For the sake of keeping the example as simple as possible, the functions are not very complicated in this case).</p> - <p>Preferably we would like to able to call <c>foo</c> and <c>bar</c> without having to bother about them actually being C functions.</p> + <p>A common interoperability situation is when you want to incorporate + a piece of code, solving a complex problem, in your Erlang + program. Suppose for example, that you have the following C + functions that you would like to call from Erlang:</p> + <codeinclude file="complex.c" tag="" type="none"></codeinclude> + <p>The functions are deliberately kept as simple as possible, for + readability reasons.</p> + <p>From an Erlang perspektive, it is preferable to be able to call + <c>foo</c> and <c>bar</c> without having to bother about that + they are C functions:</p> <pre> % Erlang code ... Res = complex:foo(X), ...</pre> - <p>The communication with C is hidden in the implementation of <c>complex.erl</c>. In the following chapters it is shown how this module can be implemented using the different interoperability mechanisms.</p> + <p>Here, the communication with C is hidden in the implementation + of <c>complex.erl</c>. + In the following sections, it is shown how this module can be + implemented using the different interoperability mechanisms.</p> </section> </chapter> |