Read about our upcoming Code of Conduct on this issue

Commit 2d53263d authored by Pierre Augier's avatar Pierre Augier
Browse files

Mention alternative syntax for blocks (issue #29)

parent f2778ef5ab38
.. Future
------
Future
------
- No need for :code:`include` and :code:`# pythran import ...`
- Alternative syntax for blocks (see `issue #29
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_)
0.1.5 (2018-12-12)
------------------
......
......@@ -296,6 +296,11 @@ export`.
`Blocks can now also be defined with type hints!
<https://fluidpythran.readthedocs.io/en/latest/examples/blocks.html>`_
.. warning ::
I'm not satisfied by the syntax for Pythran blocks so I (PA) proposed an
alternative syntax in `issue #29
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_.
Python classes: :code:`@boost` and :code:`@cachedjit` for methods
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......
Use blocks of code to define Pythran functions
==============================================
.. warning ::
I'm not satisfied by the syntax for Pythran blocks so I (PA) proposed an
alternative syntax in `issue #29
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_.
FluidPythran blocks can be used with classes and more generally in functions
with lines that cannot be compiled by Pythran.
......
......@@ -18,7 +18,7 @@ With FluidPythran, one can easily use Pythran for methods:
.. warning ::
One has to be very carreful with assignments in methods. For example,
One has to be very careful with assignments in methods. For example,
:code:`self.attr = 1` does not work but :code:`self.myarray[:] = 1` should
work (because it is not a real assignment).
......
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