Commit 49f13611 authored by Emilia Juda's avatar Emilia Juda

added content on memory management from my thesis

parent 04d3f11d
python/img/python_gc.png

19.8 KB | W: | H:

python/img/python_gc.png

19.6 KB | W: | H:

python/img/python_gc.png
python/img/python_gc.png
python/img/python_gc.png
python/img/python_gc.png
  • 2-up
  • Swipe
  • Onion skin
python/img/shared_ptr.png

18 KB | W: | H:

python/img/shared_ptr.png

18.7 KB | W: | H:

python/img/shared_ptr.png
python/img/shared_ptr.png
python/img/shared_ptr.png
python/img/shared_ptr.png
  • 2-up
  • Swipe
  • Onion skin
This diff is collapsed.
......@@ -172,10 +172,8 @@ following caveats:
\begin{itemize}
\item NumPy arrays created from Array objects will share their memory, so that
changing the C++ array changes the contents of the NumPy array. However, due
to limitations of the Array class, the converse is \emph{not true}: Arrays are
always copies of NumPy arrays.
\item Many functions in Nektar++ return Arrays through argument parameters. In
changing the C++ array changes the contents of the NumPy array.
\item Many functions in Nektar++ return Arrays through argument parameters. In
Python this is a very unnatural way to write functions. For example:
\begin{lstlisting}[language=Python]
# This is good
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment