|
From: <rom...@us...> - 2007-04-15 19:26:07
|
Revision: 991
http://svn.sourceforge.net/pygccxml/?rev=991&view=rev
Author: roman_yakovenko
Date: 2007-04-15 12:26:09 -0700 (Sun, 15 Apr 2007)
Log Message:
-----------
update docs
Modified Paths:
--------------
pyplusplus_dev/docs/troubleshooting_guide/exceptions/exceptions.rest
Modified: pyplusplus_dev/docs/troubleshooting_guide/exceptions/exceptions.rest
===================================================================
--- pyplusplus_dev/docs/troubleshooting_guide/exceptions/exceptions.rest 2007-04-15 19:24:57 UTC (rev 990)
+++ pyplusplus_dev/docs/troubleshooting_guide/exceptions/exceptions.rest 2007-04-15 19:26:09 UTC (rev 991)
@@ -16,7 +16,7 @@
It is all about module interface and user expectations. If you can translate all
your exceptions to built-in ones, than you are fine. You don't have to read this
-"lesson", but Boost.Python `exception translator`_ documentation.
+guide, but Boost.Python `exception translator`_ documentation.
.. _`exception translator` : http://boost.org/libs/python/doc/v2/exception_translator.html
@@ -47,7 +47,7 @@
Files
-----
-* `exceptions.cpp`_ file contains source code for the "lesson"
+* `exceptions.cpp`_ file contains source code for the guide
* `sconstruct`_ file contains build instructions for scons build tool.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
