pystencils issueshttps://i10git.cs.fau.de/pycodegen/pystencils/-/issues2022-05-25T10:19:32+02:00https://i10git.cs.fau.de/pycodegen/pystencils/-/issues/42Logging2022-05-25T10:19:32+02:00Markus HolzerLoggingPython provides very good logging functionality which should be used in pystencils. For example problems in the type-system could be logged on a debug level. Oftentimes it is necessary to add print statements in a debug session to see wh...Python provides very good logging functionality which should be used in pystencils. For example problems in the type-system could be logged on a debug level. Oftentimes it is necessary to add print statements in a debug session to see which expressions are cast to which type etc. This could always be logged on a debug level so we can just always see what happens in the back.
https://docs.python.org/3/howto/logging.htmlMarkus HolzerMarkus Holzerhttps://i10git.cs.fau.de/pycodegen/pystencils/-/issues/37C or C++2022-05-25T11:06:14+02:00Jan HönigC or C++I have stumbled into the issue of C vs C++ with `pystencils`. 99% we generate C code. We even would like to use the `restrict` keyword, which is only available in C, not in C++ (although many compilers do support it).
I am not sure if w...I have stumbled into the issue of C vs C++ with `pystencils`. 99% we generate C code. We even would like to use the `restrict` keyword, which is only available in C, not in C++ (although many compilers do support it).
I am not sure if we misuse C/C++ at this point. Generally C only would be beneficial, so we can include our kernels in pretty much any language, since any relevant language has a c-ffi.
What would we miss, if we would restrict ourselves on C only?
So far I have found some C++ allocations (#24), and `std::cout` usage.Markus HolzerMarkus Holzer