[pygccxml-commit] SF.net SVN: pygccxml:[1622] pyplusplus_dev/docs
Brought to you by:
mbaas,
roman_yakovenko
From: <rom...@us...> - 2009-01-26 19:49:53
|
Revision: 1622 http://pygccxml.svn.sourceforge.net/pygccxml/?rev=1622&view=rev Author: roman_yakovenko Date: 2009-01-26 19:49:49 +0000 (Mon, 26 Jan 2009) Log Message: ----------- changing alias used for C++ code blocks Modified Paths: -------------- pygccxml_dev/docs/design.rest pygccxml_dev/docs/history/history.rest pygccxml_dev/docs/query_interface.rest pygccxml_dev/docs/upgrade_issues.rest pyplusplus_dev/docs/comparisons/pyste.rest pyplusplus_dev/docs/documentation/containers.rest pyplusplus_dev/docs/documentation/ctypes/unions.rest pyplusplus_dev/docs/documentation/ctypes/variables.rest pyplusplus_dev/docs/documentation/functions/call_policies/as_tuple.rest pyplusplus_dev/docs/documentation/functions/call_policies/call_policies.rest pyplusplus_dev/docs/documentation/functions/call_policies/return_addressof.rest pyplusplus_dev/docs/documentation/functions/call_policies/return_pointee_value.rest pyplusplus_dev/docs/documentation/functions/call_policies/return_range.rest pyplusplus_dev/docs/documentation/functions/default_args.rest pyplusplus_dev/docs/documentation/functions/make_constructor.rest pyplusplus_dev/docs/documentation/functions/overloading.rest pyplusplus_dev/docs/documentation/functions/registration_order.rest pyplusplus_dev/docs/documentation/functions/transformation/inout.rest pyplusplus_dev/docs/documentation/functions/transformation/input.rest pyplusplus_dev/docs/documentation/functions/transformation/input_c_buffer.rest pyplusplus_dev/docs/documentation/functions/transformation/input_static_array.rest pyplusplus_dev/docs/documentation/functions/transformation/modify_type.rest pyplusplus_dev/docs/documentation/functions/transformation/name_mangling.rest pyplusplus_dev/docs/documentation/functions/transformation/output.rest pyplusplus_dev/docs/documentation/functions/transformation/output_static_array.rest pyplusplus_dev/docs/documentation/functions/transformation/transfer_ownership.rest pyplusplus_dev/docs/documentation/functions/transformation/transformation.rest pyplusplus_dev/docs/documentation/how_to/file_name_too_long.rest pyplusplus_dev/docs/documentation/how_to/hints.rest pyplusplus_dev/docs/documentation/how_to/templates.rest pyplusplus_dev/docs/documentation/inserting_code.rest pyplusplus_dev/docs/documentation/multi_module_development.rest pyplusplus_dev/docs/documentation/properties.rest pyplusplus_dev/docs/documentation/warnings.rest pyplusplus_dev/docs/history/history.rest pyplusplus_dev/docs/peps/dsl_challenge.rest pyplusplus_dev/docs/troubleshooting_guide/easy_extending_guide/easy_extending_guide.rest pyplusplus_dev/docs/troubleshooting_guide/shared_ptr/shared_ptr.rest Modified: pygccxml_dev/docs/design.rest =================================================================== --- pygccxml_dev/docs/design.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pygccxml_dev/docs/design.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -255,13 +255,13 @@ Well, `GCC-XML`_ has few bugs, which could not be fixed from it. For example -.. code-block:: C++ +.. code-block:: cpp namespace ns1{ namespace ns2{ enum fruit{ apple, orange }; } } -.. code-block:: C++ +.. code-block:: cpp void fix_enum( ns1::ns2::fruit arg=ns1::ns2::apple ); Modified: pygccxml_dev/docs/history/history.rest =================================================================== --- pygccxml_dev/docs/history/history.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pygccxml_dev/docs/history/history.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -47,7 +47,7 @@ Description: - .. code-block:: C++ + .. code-block:: cpp void do_smth( int, ... ) Modified: pygccxml_dev/docs/query_interface.rest =================================================================== --- pygccxml_dev/docs/query_interface.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pygccxml_dev/docs/query_interface.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -190,14 +190,14 @@ In order to help `Boost.Python`_ to manage objects life time, all functions should have `call policies`_. For example: -.. code-block:: C++ +.. code-block:: cpp struct A{ A* clone() const { return new A(); } ... }; -.. code-block:: C++ +.. code-block:: cpp struct B{ B* clone() const { return new B(); } Modified: pygccxml_dev/docs/upgrade_issues.rest =================================================================== --- pygccxml_dev/docs/upgrade_issues.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pygccxml_dev/docs/upgrade_issues.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -37,7 +37,7 @@ C++ code: -.. code-block:: C++ +.. code-block:: cpp struct xyz_t{ int do_smth( double ); @@ -85,7 +85,7 @@ For example: -.. code-block:: C++ +.. code-block:: cpp const long unsigned int initialized = 10122004; @@ -102,7 +102,7 @@ fixes some issues, but introduces another ones. Take a look on the following examples: * - .. code-block:: C++ + .. code-block:: cpp void fix_numeric( ull arg=(ull)-1 ); @@ -120,7 +120,7 @@ <Argument name="arg" type="_103" default="0xffffffffffffffffu"/> * - .. code-block:: C++ + .. code-block:: cpp void fix_function_call( int i=calc( 1,2,3) ); @@ -138,7 +138,7 @@ <Argument name="i" type="_34" default="function_call::calc(1, 2, 3)"/> * - .. code-block:: C++ + .. code-block:: cpp void typedef__func( const typedef_::alias& position = typedef_::alias() ); @@ -156,7 +156,7 @@ <Argument name="position" type="_1703" default="typedef_::original_name()"/> * - .. code-block:: C++ + .. code-block:: cpp void typedef__func2( const typedef_::alias& position = alias() ); @@ -175,7 +175,7 @@ * - .. code-block:: C++ + .. code-block:: cpp node* clone_tree( const std::vector<std::string> &types=std::vector<std::string>() ); @@ -211,7 +211,7 @@ Consider the following C++ code: -.. code-block:: C++ +.. code-block:: cpp template< unsigned long i1> struct item_t{ Modified: pyplusplus_dev/docs/comparisons/pyste.rest =================================================================== --- pyplusplus_dev/docs/comparisons/pyste.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/comparisons/pyste.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -186,15 +186,15 @@ * code creator that generates body of "overridden" virtual functions: - .. code-block:: C++ + .. code-block:: cpp struct expensive_to_copy{...}; - .. code-block:: C++ + .. code-block:: cpp void do_smth( expensive_to_copy* x, const expensive_to_copy& y ){...} - .. code-block:: C++ + .. code-block:: cpp void do_smth(expensive_to_copy* x, const expensive_to_copy& y){ @@ -332,7 +332,7 @@ * To define namespace alias. - .. code-block:: C++ + .. code-block:: cpp namespace dt = boost::date_time; @@ -341,7 +341,7 @@ * Classes and functions support 2 modes of code generation. Example: - .. code-block:: C++ + .. code-block:: cpp struct world{ void set(std::string msg) { this->msg = msg; } @@ -351,7 +351,7 @@ First mode: - .. code-block:: C++ + .. code-block:: cpp class_<world>("world") .def("greet", &world::greet) @@ -361,7 +361,7 @@ Second mode: - .. code-block:: C++ + .. code-block:: cpp if( true ){ typedef class_<world> world_exposer_t; Modified: pyplusplus_dev/docs/documentation/containers.rest =================================================================== --- pyplusplus_dev/docs/documentation/containers.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/containers.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -125,7 +125,7 @@ In this case there is no single place, where you can configure exported container functionality. Please take a look on the following C++ code: -.. code-block:: C++ +.. code-block:: cpp struct item{ ... Modified: pyplusplus_dev/docs/documentation/ctypes/unions.rest =================================================================== --- pyplusplus_dev/docs/documentation/ctypes/unions.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/ctypes/unions.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -22,7 +22,7 @@ For this example I am going to use the following code: - .. code-block:: C++ + .. code-block:: cpp struct data_t{ union actual_data_t{ Modified: pyplusplus_dev/docs/documentation/ctypes/variables.rest =================================================================== --- pyplusplus_dev/docs/documentation/ctypes/variables.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/ctypes/variables.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -21,7 +21,7 @@ Lets say you have the following C++ code: - .. code-block:: C++ + .. code-block:: cpp struct bytes_t{ bytes_t(){ Modified: pyplusplus_dev/docs/documentation/functions/call_policies/as_tuple.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/call_policies/as_tuple.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/call_policies/as_tuple.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -16,7 +16,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct vector3{ ... Modified: pyplusplus_dev/docs/documentation/functions/call_policies/call_policies.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/call_policies/call_policies.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/call_policies/call_policies.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -21,7 +21,7 @@ The call policies in `Py++`_ are named exactly as in `Boost.Python`_, only the syntax is slightly different. For instance, this call policy: -.. code-block:: C++ +.. code-block:: cpp return_internal_reference< 1, with_custodian_and_ward<1, 2> >() @@ -41,7 +41,7 @@ C++ code: - .. code-block:: C++ + .. code-block:: cpp struct data{...}; const data& do_smth( const data& d, int x ); @@ -130,7 +130,7 @@ * `Py++`_ generates code with - .. code-block:: C++ + .. code-block:: cpp /* undefined call policies */ @@ -157,7 +157,7 @@ Example: -.. code-block:: C++ +.. code-block:: cpp struct identity_impl_t{}; typedef identity_impl_t* identity; Modified: pyplusplus_dev/docs/documentation/functions/call_policies/return_addressof.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/call_policies/return_addressof.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/call_policies/return_addressof.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -21,7 +21,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp int* get_value(){ static int buffer[] = { 0,1,2,3,4 }; Modified: pyplusplus_dev/docs/documentation/functions/call_policies/return_pointee_value.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/call_policies/return_pointee_value.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/call_policies/return_pointee_value.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -12,7 +12,7 @@ can be used to wrap C++ functions, that return a pointer to a C++ object. The policy implements the following logic: -.. code-block:: C++ +.. code-block:: cpp if( <<<return value is NULL pointer>>> ){ return None; @@ -46,7 +46,7 @@ This technique and example was contributed by Maximilian Matthe. -.. code-block:: C++ +.. code-block:: cpp struct int_wrapper{ int_wrapper(int v) @@ -93,7 +93,7 @@ Return pointee value -------------------- -.. code-block:: C++ +.. code-block:: cpp float* get_value(){ static float value = 0.5; Modified: pyplusplus_dev/docs/documentation/functions/call_policies/return_range.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/call_policies/return_range.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/call_policies/return_range.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -18,7 +18,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct image_t{ @@ -49,7 +49,7 @@ ``return_range`` class ---------------------- -.. code-block:: C++ +.. code-block:: cpp template < typename TGetSize , typename TValueType @@ -80,7 +80,7 @@ * call operator with the following signature: - .. code-block:: C++ + .. code-block:: cpp ssize_t operator()( boost::python::tuple args ); @@ -91,7 +91,7 @@ For our case, the following class could be defined: -.. code-block:: C++ +.. code-block:: cpp struct image_data_size_t{ ssize_t operator()( boost::python::tuple args ){ @@ -105,7 +105,7 @@ Passing all arguments, instead of single "self" argument gives you an ability to treat functions, where the user asked to get access to the part of the array. -.. code-block:: C++ +.. code-block:: cpp struct image_t{ ... @@ -119,7 +119,7 @@ The following "get size" class treats this situation: -.. code-block:: C++ +.. code-block:: cpp struct image_data_size_t{ ssize_t operator()( boost::python::tuple args ){ @@ -151,7 +151,7 @@ I think, now you are ready to see the whole solution: -.. code-block:: C++ +.. code-block:: cpp namespace bpl = boost::python; namespace ppc = pyplusplus::call_policies; Modified: pyplusplus_dev/docs/documentation/functions/default_args.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/default_args.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/default_args.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -11,7 +11,7 @@ There is more than one way to export function with default arguments. Before we proceed, please take a look on the following class: -.. code-block:: C++ +.. code-block:: cpp struct X { @@ -27,7 +27,7 @@ By default `Py++`_ exposes function with its default arguments. -.. code-block:: C++ +.. code-block:: cpp namespace bp = boost::python; @@ -71,7 +71,7 @@ There is different trades-off between these approaches. In general you should use the first one, until you have "registration order" problem: -.. code-block:: C++ +.. code-block:: cpp struct S1; struct S2; @@ -122,7 +122,7 @@ Class constructors are special case: -.. code-block:: C++ +.. code-block:: cpp struct S1; struct S2; Modified: pyplusplus_dev/docs/documentation/functions/make_constructor.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/make_constructor.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/make_constructor.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -19,7 +19,7 @@ ------------- I am going to use the following code to demonstrate the functionality: -.. code-block:: C++ +.. code-block:: cpp #include <memory> Modified: pyplusplus_dev/docs/documentation/functions/overloading.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/overloading.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/overloading.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -13,7 +13,7 @@ want to export, by specifying its type. Before we proceed, please take a look on the following class: -.. code-block:: C++ +.. code-block:: cpp struct X { @@ -46,7 +46,7 @@ I am sure you will like "do nothing" approach. `Py++`_ recognize that you want to export an overloaded function and will generate the right code: -.. code-block:: C++ +.. code-block:: cpp namespace bp = boost::python; @@ -82,7 +82,7 @@ It is very important to understand it. Lets take a look on the following source code: -.. code-block:: C++ +.. code-block:: cpp struct Y{ Modified: pyplusplus_dev/docs/documentation/functions/registration_order.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/registration_order.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/registration_order.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -22,7 +22,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct tester_t{ tester_t() {} @@ -43,7 +43,7 @@ `Py++`_ generates code, that register functions in the order they appear in the source code: -.. code-block:: C++ +.. code-block:: cpp namespace bp = boost::python; Modified: pyplusplus_dev/docs/documentation/functions/transformation/inout.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/inout.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/inout.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -24,7 +24,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp #include <string> @@ -47,7 +47,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; Modified: pyplusplus_dev/docs/documentation/functions/transformation/input.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/input.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/input.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -18,7 +18,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp #include <string> @@ -41,7 +41,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; Modified: pyplusplus_dev/docs/documentation/functions/transformation/input_c_buffer.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/input_c_buffer.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/input_c_buffer.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -20,7 +20,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct file_t{ void write( char* buffer, int size ) const; @@ -40,7 +40,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp #include "__convenience.pypp.hpp" //Py++ header file, which contains few convenience function Modified: pyplusplus_dev/docs/documentation/functions/transformation/input_static_array.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/input_static_array.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/input_static_array.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -20,7 +20,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct vector3{ @@ -47,7 +47,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp #include "__convenience.pypp.hpp" //Py++ header file, which contains few convenience function Modified: pyplusplus_dev/docs/documentation/functions/transformation/modify_type.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/modify_type.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/modify_type.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -28,7 +28,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp #include <string> @@ -52,7 +52,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; Modified: pyplusplus_dev/docs/documentation/functions/transformation/name_mangling.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/name_mangling.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/name_mangling.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -20,7 +20,7 @@ name mangling to create function-wrappers for overloaded and\\or free functions. Consider the following use case: - .. code-block:: C++ + .. code-block:: cpp void get_distance( long& ); void get_distance( double& ); @@ -28,7 +28,7 @@ In order to expose ``get_distance`` functions you have to create 2 function wrappers: - .. code-block:: C++ + .. code-block:: cpp long get_distance_as_long(){...} double get_distance_as_double(){...} @@ -37,7 +37,7 @@ on return type only. You also have to exposes them under different aliases, otherwise they will not be callable from `Python`_: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; BOOST_PYTHON_MODULE(...){ Modified: pyplusplus_dev/docs/documentation/functions/transformation/output.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/output.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/output.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -20,7 +20,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp #include <string> @@ -43,7 +43,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; Modified: pyplusplus_dev/docs/documentation/functions/transformation/output_static_array.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/output_static_array.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/output_static_array.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -19,7 +19,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct vector3{ @@ -46,7 +46,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp #include "__convenience.pypp.hpp" //Py++ header file, which contains few convenience function Modified: pyplusplus_dev/docs/documentation/functions/transformation/transfer_ownership.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/transfer_ownership.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/transfer_ownership.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -24,7 +24,7 @@ Example ------- -.. code-block:: C++ +.. code-block:: cpp struct resource_t{...}; @@ -51,7 +51,7 @@ What you see below is the relevant pieces of generated code: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; Modified: pyplusplus_dev/docs/documentation/functions/transformation/transformation.rest =================================================================== --- pyplusplus_dev/docs/documentation/functions/transformation/transformation.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/functions/transformation/transformation.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -15,7 +15,7 @@ An often mentioned example that demonstrates the problem is the ``get_size()`` member function of a fictitious image class: -.. code-block:: C++ +.. code-block:: cpp void get_size(int& width, int& height); @@ -31,7 +31,7 @@ and the wrapper could look like this: -.. code-block:: C++ +.. code-block:: cpp boost::python::tuple get_size( const image_t& img ){ int width; Modified: pyplusplus_dev/docs/documentation/how_to/file_name_too_long.rest =================================================================== --- pyplusplus_dev/docs/documentation/how_to/file_name_too_long.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/how_to/file_name_too_long.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -13,7 +13,7 @@ Let me explain. -.. code-block:: C++ +.. code-block:: cpp template < class T> struct holder{ ... }; Modified: pyplusplus_dev/docs/documentation/how_to/hints.rest =================================================================== --- pyplusplus_dev/docs/documentation/how_to/hints.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/how_to/hints.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -13,7 +13,7 @@ For example: -.. code-block:: C++ +.. code-block:: cpp #include <vector> typedef std::vector< int > numbers; @@ -23,7 +23,7 @@ `Py++`_ will use "numbers" as Python class name: -.. code-block:: C++ +.. code-block:: cpp using boost::python; class_< std::vector< int > >( "numbers" ) @@ -38,7 +38,7 @@ The previous approach is "implicit" - `Py++`_ does something behind the scene. Recently (version 0.8.6 ), another approach was introduced: -.. code-block:: C++ +.. code-block:: cpp #include <vector> Modified: pyplusplus_dev/docs/documentation/how_to/templates.rest =================================================================== --- pyplusplus_dev/docs/documentation/how_to/templates.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/how_to/templates.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -10,7 +10,7 @@ I would like to introduce the following piece of code. I am going to use it for most exlanations. -.. code-block:: C++ +.. code-block:: cpp // file point.h template< class T> @@ -39,14 +39,14 @@ You can instantiate template class using operator ``sizeof``: -.. code-block:: C++ +.. code-block:: cpp sizeof( point_t<int> ); In order to instantiate a function you have to call it: -.. code-block:: C++ +.. code-block:: cpp void instantiate(){ double x = distance( point_t<t>() ); @@ -83,7 +83,7 @@ Functions templated on return type ---------------------------------- -.. code-block:: C++ +.. code-block:: cpp environment_t env; std::string path = env.get_value< std::string >( "PATH" ); @@ -105,7 +105,7 @@ Generated code: -.. code-block:: C++ +.. code-block:: cpp bp::class_< environment_t >( "environment_t" ) ... @@ -116,7 +116,7 @@ The correct code: -.. code-block:: C++ +.. code-block:: cpp bp::class_< environment_t >( "environment_t" ) .def( "get_value" @@ -128,7 +128,7 @@ The perfect one: -.. code-block:: C++ +.. code-block:: cpp bp::class_< environment_t >( "environment_t" ) ... Modified: pyplusplus_dev/docs/documentation/inserting_code.rest =================================================================== --- pyplusplus_dev/docs/documentation/inserting_code.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/inserting_code.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -18,7 +18,7 @@ Almost every ``Boost.Python`` module has the following structure: -.. code-block:: C++ +.. code-block:: cpp //declarations code ... @@ -60,7 +60,7 @@ ``class_t`` declaration defines few methods, which add user code to the generated one. Lets take a look on the following use case: -.. code-block:: C++ +.. code-block:: cpp struct window_t{ ... @@ -74,7 +74,7 @@ In the near future `Py++`_ will eliminate the need of creating hand written wrapper for this use case. -.. code-block:: C++ +.. code-block:: cpp boost::python::tuple get_window_size( const window_t& win ){ int h(0), w(0); @@ -84,7 +84,7 @@ Now you have to register it: -.. code-block:: C++ +.. code-block:: cpp using boost::python; class_< window_t >( ... ) @@ -121,7 +121,7 @@ If you will pass ``works_on_instance=False`` the following code will be generated: - .. code-block:: C++ + .. code-block:: cpp { class_< window_t > window_exporter( "window_t" ); @@ -132,7 +132,7 @@ And in this case, user will be forced to pass reference to ``window_t`` object: - .. code-block:: C++ + .. code-block:: cpp win = window_t() height, width = window_t.get_size( win ) Modified: pyplusplus_dev/docs/documentation/multi_module_development.rest =================================================================== --- pyplusplus_dev/docs/documentation/multi_module_development.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/multi_module_development.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -29,7 +29,7 @@ The code: -.. code-block:: C++ +.. code-block:: cpp namespace core{ class image_i{ @@ -72,7 +72,7 @@ `Py++`_ will generate code very similar to the the following one: -.. code-block:: C++ +.. code-block:: cpp //file core.cpp namespace bp = boost::python; @@ -95,7 +95,7 @@ .def( "load", bp::pure_virtual( &::core::image_i::load ) ); } -.. code-block:: C++ +.. code-block:: cpp //file png.cpp struct png_image_t_wrapper : png::png_image_t, bp::wrapper< png::png_image_t > { Modified: pyplusplus_dev/docs/documentation/properties.rest =================================================================== --- pyplusplus_dev/docs/documentation/properties.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/properties.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -19,7 +19,7 @@ Usage example ------------- -.. code-block:: C++ +.. code-block:: cpp struct number{ ... @@ -63,11 +63,11 @@ Consider the following use case: -.. code-block:: C++ +.. code-block:: cpp struct nested{ ... }; -.. code-block:: C++ +.. code-block:: cpp struct data{ ... Modified: pyplusplus_dev/docs/documentation/warnings.rest =================================================================== --- pyplusplus_dev/docs/documentation/warnings.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/documentation/warnings.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -24,11 +24,11 @@ some cases provide hints about how to resolve the problem. Few examples: * - .. code-block:: C++ + .. code-block:: cpp struct Y{ ... }; - .. code-block:: C++ + .. code-block:: cpp struct X{ ... @@ -38,7 +38,7 @@ Member function ``do_smth`` cannot be overridden in Python because ... . * - .. code-block:: C++ + .. code-block:: cpp struct window{ ... @@ -51,7 +51,7 @@ should define ``BOOST_PYTHON_MAX_ARITY`` macro. * - .. code-block:: C++ + .. code-block:: cpp struct X{ ... Modified: pyplusplus_dev/docs/history/history.rest =================================================================== --- pyplusplus_dev/docs/history/history.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/history/history.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -45,7 +45,7 @@ The change explanation. - .. code-block:: C++ + .. code-block:: cpp struct A{ virtual void foo() {} @@ -75,7 +75,7 @@ If you use "function transformation" functionality, than it is possible the generated code will **NOT** work. Consider the following example: - .. code-block:: C++ + .. code-block:: cpp struct A{ virtual void foo(int& i) {/*do smth*/} @@ -98,7 +98,7 @@ The generated code, for class ``B``, is: - .. code-block:: C++ + .. code-block:: cpp namespace bp = boost::python; @@ -512,7 +512,7 @@ 8. `Py++`_ now generates correct code for hierarchy of abstract classes: - .. code-block:: C++ + .. code-block:: cpp struct abstract1{ virtual void do_smth() = 0; Modified: pyplusplus_dev/docs/peps/dsl_challenge.rest =================================================================== --- pyplusplus_dev/docs/peps/dsl_challenge.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/peps/dsl_challenge.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -16,7 +16,7 @@ I will use the following C++ code as an example: -.. code-block:: C++ +.. code-block:: cpp namespace geometry{ struct Point{ @@ -105,7 +105,7 @@ B-API does not work for template instantiated classes and functions. If we change class ``Point`` to be template, the special syntax should be introduced: - .. code-block:: C++ + .. code-block:: cpp template < class Numeric > struct Point{ @@ -119,7 +119,7 @@ This is a trivial example, which is why it looks great. Consider the following class: - .. code-block:: C++ + .. code-block:: cpp template< class String, class Allocator > class regex{ ... } Modified: pyplusplus_dev/docs/troubleshooting_guide/easy_extending_guide/easy_extending_guide.rest =================================================================== --- pyplusplus_dev/docs/troubleshooting_guide/easy_extending_guide/easy_extending_guide.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/troubleshooting_guide/easy_extending_guide/easy_extending_guide.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -38,7 +38,7 @@ Consider the following function: -.. code-block:: C++ +.. code-block:: cpp int write( int* data, size_t size ); Modified: pyplusplus_dev/docs/troubleshooting_guide/shared_ptr/shared_ptr.rest =================================================================== --- pyplusplus_dev/docs/troubleshooting_guide/shared_ptr/shared_ptr.rest 2009-01-26 15:03:04 UTC (rev 1621) +++ pyplusplus_dev/docs/troubleshooting_guide/shared_ptr/shared_ptr.rest 2009-01-26 19:49:49 UTC (rev 1622) @@ -20,7 +20,7 @@ It is also possible to solve the problem, without changing Boost.Python library: - .. code-block:: C++ + .. code-block:: cpp namespace boost{ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |