/Src/Dependencies/Boost/libs/phoenix/doc/html/phoenix/introduction.html

http://hadesmem.googlecode.com/ · HTML · 70 lines · 70 code · 0 blank · 0 comment · 0 complexity · 5ed19dcbf5c8a24eda3ad8a7cbc63e42 MD5 · raw file 

    

  1. <html>
    2. 

  2. <head>
    3. 

  3. <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
    4. 

  4. <title>Introduction</title>
    5. 

  5. <link rel="stylesheet" href="../../../../../doc/src/boostbook.css" type="text/css">
    6. 

  6. <meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
    7. 

  7. <link rel="home" href="../index.html" title="Chapter&#160;1.&#160;Phoenix 3.0">
    8. 

  8. <link rel="up" href="../index.html" title="Chapter&#160;1.&#160;Phoenix 3.0">
    9. 

  9. <link rel="prev" href="what_s_new/phoenix_3_0.html" title="Phoenix 3.0">
    10. 

  10. <link rel="next" href="starter_kit.html" title="Starter Kit">
    11. 

  11. </head>
    12. 

  12. <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
    13. 

  13. <table cellpadding="2" width="100%"><tr>
    14. 

  14. <td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../../boost.png"></td>
    15. 

  15. <td align="center"><a href="../../../../../index.html">Home</a></td>
    16. 

  16. <td align="center"><a href="../../../../../libs/libraries.htm">Libraries</a></td>
    17. 

  17. <td align="center"><a href="http://www.boost.org/users/people.html">People</a></td>
    18. 

  18. <td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td>
    19. 

  19. <td align="center"><a href="../../../../../more/index.htm">More</a></td>
    20. 

  20. </tr></table>
    21. 

  21. <hr>
    22. 

  22. <div class="spirit-nav">
    23. 

  23. <a accesskey="p" href="what_s_new/phoenix_3_0.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="starter_kit.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
    24. 

  24. </div>
    25. 

  25. <div class="section">
    26. 

  26. <div class="titlepage"><div><div><h2 class="title" style="clear: both">
    27. 

  27. <a name="phoenix.introduction"></a><a class="link" href="introduction.html" title="Introduction">Introduction</a>
    28. 

  28. </h2></div></div></div>
    29. 

  29. <p>
    30. 

  30.       <span class="inlinemediaobject"><img src="../images/banner.png" alt="banner"></span>
    31. 

  31.     </p>
    32. 

  32. <p>
    33. 

  33.       The Phoenix library enables FP techniques such as higher order functions,
    34. 

  34.       <span class="emphasis"><em>lambda</em></span> (unnamed functions), <span class="emphasis"><em>currying</em></span>
    35. 

  35.       (partial function application) and lazy evaluation in C++. The focus is more
    36. 

  36.       on usefulness and practicality than purity, elegance and strict adherence to
    37. 

  37.       FP principles.
    38. 

  38.     </p>
    39. 

  39. <p>
    40. 

  40.       FP is a programming discipline that is not at all tied to a specific language.
    41. 

  41.       FP as a programming discipline can, in fact, be applied to many programming
    42. 

  42.       languages. In the realm of C++ for instance, we are seeing more FP techniques
    43. 

  43.       being applied. C++ is sufficiently rich to support at least some of the most
    44. 

  44.       important facets of FP. C++ is a multiparadigm programming language. It is
    45. 

  45.       not only procedural. It is not only object oriented. Beneath the core of the
    46. 

  46.       standard C++ library, a closer look into STL gives us a glimpse of FP already
    47. 

  47.       in place. It is obvious that the authors of STL know and practice FP. In the
    48. 

  48.       near future, we shall surely see more FP trickle down into the mainstream.
    49. 

  49.     </p>
    50. 

  50. <p>
    51. 

  51.       The truth is, most of the FP techniques can coexist quite well with the standard
    52. 

  52.       object oriented and imperative programming paradigms. When we are using STL
    53. 

  53.       algorithms and functors (function objects) for example, we are already doing
    54. 

  54.       FP. Phoenix is an evolutionary next step.
    55. 

  55.     </p>
    56. 

  56. </div>
    57. 

  57. <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
    58. 

  58. <td align="left"></td>
    59. 

  59. <td align="right"><div class="copyright-footer">Copyright &#169; 2002-2005, 2010 Joel de Guzman, Dan Marsden, Thomas Heller<p>
    60. 

  60.         Distributed under the Boost Software License, Version 1.0. (See accompanying
    61. 

  61.         file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
    62. 

  62.       </p>
    63. 

  63. </div></td>
    64. 

  64. </tr></table>
    65. 

  65. <hr>
    66. 

  66. <div class="spirit-nav">
    67. 

  67. <a accesskey="p" href="what_s_new/phoenix_3_0.html"><img src="../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="starter_kit.html"><img src="../../../../../doc/src/images/next.png" alt="Next"></a>
    68. 

  68. </div>
    69. 

  69. </body>
    70. 

  70. </html>
    71.