ceph/src/boost/libs/phoenix/doc/wrap_up.qbk

   1 [/==============================================================================
   2     Copyright (C) 2001-2010 Joel de Guzman
   3     Copyright (C) 2001-2005 Dan Marsden
   4     Copyright (C) 2001-2010 Thomas Heller
   5
   6     Distributed under the Boost Software License, Version 1.0. (See accompanying
   7     file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
   8 ===============================================================================/]
   9
  10 [section Wrap Up]
  11
  12 Sooner or later more FP techniques become standard practice as people find the
  13 true value of this programming discipline outside the academe and into the
  14 mainstream. In as much as structured programming of the 70s and object oriented
  15 programming in the 80s and generic programming in the 90s shaped our thoughts
  16 towards a more robust sense of software engineering, FP will certainly be a
  17 paradigm that will catapult us towards more powerful software design and
  18 engineering onward into the new millennium.
  19
  20 Let me quote Doug Gregor of Boost.org. About functional style programming
  21 libraries:
  22
  23 [:['They're gaining acceptance, but are somewhat stunted by the ubiquitousness
  24 of broken compilers. The C++ community is moving deeper into the so-called "STL-
  25 style" programming paradigm, which brings many aspects of functional programming
  26 into the fold. Look at, for instance, the Spirit parser to see how such function
  27 objects can be used to build Yacc-like grammars with semantic actions that can
  28 build abstract syntax trees on the fly. This type of functional composition is
  29 gaining momentum.]]
  30
  31 Indeed. Phoenix is another attempt to introduce more FP techniques into the
  32 mainstream. Not only is it a tool that will make life easier for the programmer.
  33 In its own right, the actual design of the library itself is a model of true C++
  34 FP in action. The library is designed and structured in a strict but clear and
  35 well mannered FP sense. By all means, use the library as a tool. But for those
  36 who want to learn more about FP in C++, don't stop there, I invite you to take a
  37 closer look at the design of the library itself.
  38
  39 So there you have it. Have fun! See you in the FP world.
  40
  41 [endsect]