Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc user_guide: Minor wording tweak #65

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

doc user_guide: Minor wording tweak #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/user_guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Problem setting
---------------

Consider a scientist who has designed multiple *C++* libraries for statistical analysis.
He would like to distribute his libraries and decide to make them available in *Python* in order to reach a public of statisticians but also less expert scientists such as biologists.
He would like to distribute his libraries and decide to make them available in *Python* in order to reach a public of scientists, expert and non-expert programmers alike.
Yet, he is not interested in becoming an expert in *C++*/*Python* wrapping, even if it exists classical approaches consisting in writing wrappers with **SWIG** :cite:`Bea03` or **Boost.Python** :cite:`AG03`.
Moreover, he would have serious difficulties to maintain the wrappers, since this semi-automatic process is time consuming and error prone.
Instead, he would like to automate the process of generating wrappers in sync with his evolving *C++* libraries.
Expand Down