[pygccxml-commit] source/pyplusplus __init__.py,1.27,1.28

[Roman <rom...@us...>]

Update of /cvsroot/pygccxml/source/pyplusplus
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6005/pyplusplus

Modified Files:
	__init__.py 
Log Message:
I was ill and did not have my TortoiseCVS :-). 
This commit contains documentation changes only. 
Those changes had been done for latest release version.

Index: __init__.py
===================================================================
RCS file: /cvsroot/pygccxml/source/pyplusplus/__init__.py,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -d -r1.27 -r1.28
*** __init__.py	9 Apr 2006 06:55:14 -0000	1.27
--- __init__.py	20 Apr 2006 04:06:41 -0000	1.28
***************
*** 15,40 ****
  in the headers. You can then modify (decorate) this tree to customize
  the bindings. After that, a I{code creators} tree is created where
! each node represents a block of C++ source code. As a last step, these
! source code blocks are finally written into one or more C++ source
! files which can then be compiled to generate the final Python module.
! 
! In general, the following steps have to be done:
! 
!  1. B{Parsing the header files}: This is done by the pygccxml package.
!     You either use the pygccxml.parser.parse() function or the
!     pygccxml.parser.project_reader_t class.    
!     Note: Currently, you B{must} pass a L{dwfactory_t<decl_wrappers.dwfactory_t>}
!     object to the parser so that the resulting declaration tree is composed
!     of the decl_wrapper nodes in the L{decl_wrappers} sub-package instead
!     of the declaration nodes from pygccxml.
! 
!  2. B{Creating the code creators tree}: This is done by the
!     L{creator_t<module_creator.creator_t>} class in the L{module_creator}
!     sub-package. The code creators tree is composed of the nodes defined
!     in the L{code_creators} sub-package.
! 
!  3. B{Writing the source files}: This is done by the functions in the
!     L{file_writers} sub-package.
  
  """
  
--- 15,25 ----
  in the headers. You can then modify (decorate) this tree to customize
  the bindings. After that, a I{code creators} tree is created where
! each node represents a block of C++ source code. So you can change any piece of
! code befor it is written to disk. As a last step, these source code blocks are 
! finally written into one or more C++ source files, which can then be compiled to 
! generate the final Python module.
  
+ If you are just starting with U{pyplusplus<http://www.language-binding.net>}, 
+ then consider to read documentation of L{module_builder} package.
  """