delta/cython.git/docs/examples/tutorial, branch master github.com: cython/cython.git [docs] Softdeprecated C style array declaration in favour of Java style declaration (#5248) 2023-02-18T12:32:46+00:00 Matus Valo matusvalo@users.noreply.github.com 2023-02-18T12:32:46+00:00 cf9c2f07de36ecc4e4aa21999a7e7982df59b881 Co-authored-by: GalaxySnail <me@glxys.nl> 
Co-authored-by: GalaxySnail <me@glxys.nl>
 [docs] Parallelization tutorial (#5184) 2023-02-06T17:21:34+00:00 da-woods dw-git@d-woods.co.uk 2023-02-06T17:21:34+00:00 b24286d35aaaf1318cd2bebb10e3e16d72965a5b Parallelization tutorial to try to explain prange/parallel in a little more user-friendly way 
Parallelization tutorial to try to explain prange/parallel in a little more user-friendly way
 Fix linkage for `cdef public` functions in C++ mode (#5040) 2022-11-08T21:30:07+00:00 Maximilien Colange 111890372+EpigeneMax@users.noreply.github.com 2022-11-08T21:30:07+00:00 2d40828375f2a25a4b931e582bf0ad5161926e42 Fixes #1839 cdef public functions should be declared with the appropriate linkage: * in C mode, either extern or extern "C", depending on whether the header file is included in (resp. object code is linked against) a C or a C++ compilation unit. Choice is made at compile-time through #ifdef __cplusplus macros. NB: This is the current behavior. * in C++ mode, extern "C++" is the only option, as C code cannot call C++ code. Note that extern "C++" should be preferred over extern to allow users to #include the C++ header inside a extern "C" block (which is legal, although barely used). Note that the current behavior is OK for C mode, but is incorrect for the C++ mode. As described in #1839, this incorrect behavior is diagnosed by compilers emitting warnings when cdef public functions return a C++ type (e.g. std::vector). The test introduced in this PR checks that the current behavior for C mode (with both C and C++ compatibility) is preserved, and that the behavior for C++ mode is fixed. 
Fixes #1839

cdef public functions should be declared with the appropriate linkage:

* in C mode, either extern or extern "C", depending on whether the header file is included in (resp. object code is linked against) a C or a C++ compilation unit. Choice is made at compile-time through #ifdef __cplusplus macros. NB: This is the current behavior.
* in C++ mode, extern "C++" is the only option, as C code cannot call C++ code. Note that extern "C++" should be preferred over extern to allow users to #include the C++ header inside a extern "C" block (which is legal, although barely used).

Note that the current behavior is OK for C mode, but is incorrect for the C++ mode. As described in #1839, this incorrect behavior is diagnosed by compilers emitting warnings when cdef public functions return a C++ type (e.g. std::vector).
The test introduced in this PR checks that the current behavior for C mode (with both C and C++ compatibility) is preserved, and that the behavior for C++ mode is fixed.
[Doc] Improve documentation of disabling annotations in pure mode (#5080) 2022-10-12T16:48:59+00:00 Matus Valo matusvalo@users.noreply.github.com 2022-10-12T16:48:59+00:00 4eacb83cbb4ff496f4fc1bc37b98aaf424823a27 






Use annotation for pointer in docs (#4942)
2022-08-02T20:45:08+00:00

Matus Valo
matusvalo@users.noreply.github.com

2022-08-02T20:45:08+00:00

f51d258e74ea0ab073507f05e5f1550cc457c8d7

and remove note about bug




and remove note about bug






[docs] Fix typo in embedded.pyx
2022-07-27T15:05:44+00:00

da-woods
dw-git@d-woods.co.uk

2022-07-27T15:05:44+00:00

7d59ffaebe08914681067458d8e5c5288e13fe4d












docs: pythonise "Working with Python arrays" (array.rst) (GH-4431)
2022-02-02T17:16:24+00:00

0dminnimda
0dminnimda@gmail.com

2022-02-02T17:16:24+00:00

14150abda758ce19b6387fa877063f6d5f9a4584












Docs: Migrate profiling tutorial to pure Python (GH-4311)
2021-12-14T13:18:17+00:00

Matus Valo
matusvalo@users.noreply.github.com

2021-12-14T13:18:17+00:00

0dffecfa4407b761ba138a6bbcfcffcd65454aa8












Add "import_array()" to the Numpy tutorial (GH-4403)
2021-11-02T09:57:05+00:00

da-woods
dw-git@d-woods.co.uk

2021-11-02T09:57:05+00:00

00ffb022f82cf13a055102288ca5c1b299f4ecdc

Arguably, it's unnecessary if the auto-call works correctly, but if we're still advising users to do it themselves then it probably should be in the docs.




Arguably, it's unnecessary if the auto-call works correctly, but if we're still advising users to do it themselves then it probably should be in the docs.






docs: Pythonise documentation on Memory Allocation (memory_allocation.rst) (GH-4316)
2021-08-08T08:30:07+00:00

0dminnimda
0dminnimda@gmail.com

2021-08-08T08:30:07+00:00

3a0ca192ed497f81c7bee60f13f635c9ac265e72