emu387.xml 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. <?xml version="1.0" encoding="ISO8859-1"?>
  2. <fpdoc-descriptions>
  3. <!--
  4. $Id$
  5. This file is part of the FPC documentation.
  6. Copyright (C) 1997, by Michael Van Canneyt
  7. The FPC documentation is free text; you can redistribute it and/or
  8. modify it under the terms of the GNU Library General Public License as
  9. published by the Free Software Foundation; either version 2 of the
  10. License, or (at your option) any later version.
  11. The FPC Documentation is distributed in the hope that it will be useful,
  12. but WITHOUT ANY WARRANTY; without even the implied warranty of
  13. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  14. Library General Public License for more details.
  15. You should have received a copy of the GNU Library General Public
  16. License along with the FPC documentation; see the file COPYING.LIB. If not,
  17. write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
  18. Boston, MA 02111-1307, USA.
  19. -->
  20. <package name="rtl">
  21. <module name="emu387">
  22. <short>Load coprocessor emulation support</short>
  23. <descr>
  24. <p>
  25. The <file>emu387</file> unit was written by Pierre Mueller for dos. It
  26. sets up the coprocessor emulation for FPC under dos. It is not necessary to
  27. use this unit on other OS platforms because they either simply do not run on
  28. a machine without coprocessor, or they provide the coprocessor emulation
  29. themselves.
  30. </p>
  31. <p>
  32. It shouldn't be necessary to use the function in this unit, it should be
  33. enough to place this unit in the <var>uses</var> clause of your program to
  34. enable the coprocessor emulation under dos. The unit initialization
  35. code will try and load the coprocessor emulation code and initialize it.
  36. </p>
  37. </descr>
  38. <element name="npxsetup">
  39. <short>Set up coprocessor emulation.</short>
  40. <descr>
  41. <p>
  42. <var>npxsetup</var> checks whether a coprocessor is found. If not, it loads the
  43. file <file>wmemu387.dxe</file> into memory and initializes the code in it.
  44. </p>
  45. <p>
  46. If the environment variable <var>387</var> is set to <var>N</var>, then the emulation
  47. will be loaded, even if there is a coprocessor present. If the variable
  48. doesn't exist, or is set to any other value, the unit will try to detect
  49. the presence of a coprocessor unit.
  50. </p>
  51. <p>
  52. The function searches the file <file>wmemu387.dxe</file> in the following way:
  53. </p>
  54. <ol>
  55. <li> If the environment variable <var>EMU387</var> is set, then it is assumed
  56. to point at the <file>wmemu387.dxe</file> file.
  57. </li>
  58. <li> if the environment variable <var>EMU387</var> does not exist, then the
  59. function will take the path part of <var>prog_name</var> and look in that
  60. directory for the file <file>wmemu387.dxe</file>.
  61. </li>
  62. </ol>
  63. <p>
  64. It should never be necessary to call this function, because the
  65. initialization code of the unit contains a call to the function with
  66. as an argument <var>paramstr(0)</var>. This means that you should deliver the
  67. file <var>wmemu387.dxe</var> together with your program.
  68. </p>
  69. </descr>
  70. <errors>
  71. If there is an error, an error message is printed to standard error, and
  72. the program is halted, since any floating-point code is bound to fail anyhow.
  73. </errors>
  74. </element>
  75. </module>
  76. </package>
  77. </fpdoc-descriptions>