boost/python
2
0
Fork 0
mirror of https://github.com/boostorg/python.git synced 2026-01-30 08:02:38 +00:00
Code Issues Projects Releases Wiki Activity

py_cpp => Boost.Python

Browse Source 
[SVN r9485]
This commit is contained in:
Dave Abrahams
2001-03-08 03:01:29 +00:00
parent bdbd9a0f5f
commit a559480716
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/overriding.html
View File

@@ -92,7 +92,7 @@ struct hello_callback : hello
<p>
Finally, we add <tt>hello_callback</tt> to the <tt>
class_builder&lt;&gt;</tt> declaration in our module initialization
function, and when we define the function, we must tell py_cpp about the default
function, and when we define the function, we must tell Boost.Python about the default
implementation:
<blockquote><pre>
@@ -120,7 +120,7 @@ hello_class.def(&amp;hello::greet, "greet", &amp;<b>hello_callback::default_gree
<p>
<a name="why_derived">*</a>You may ask, "Why do we need this derived
class? This could have been designed so that everything gets done right
inside of <tt>hello</tt>." One of the goals of py_cpp is to be
inside of <tt>hello</tt>." One of the goals of Boost.Python is to be
minimally intrusive on an existing C++ design. In principle, it should be
possible to expose the interface for a 3rd party library without changing
it. To unintrusively hook into the virtual functions so that a Python