Robert Maxton

For future readers: indeed, it is sort of implemented already; it seems that some of this information (raw amplitude data rather than measurements) is available under `save_state()`.

Wanted to re-open this - Do we have a solution yet? Would like to avoid trying to use the Curse client on my server, since I'm ssh'ing into it and...

Workaround -- by rewriting my code so that it reads ```C++ } #include extern "C" { .... ``` I can avoid including the `#include` in the `extern "C"` without giving...

Basically, PyCUDA provides no way to `#include` additional header files outside `extern "C`, except by turning off `extern "C"` entirely. There's also (AFAIK) no way to get a list of...

Well, perhaps we could have a `header` option in the constructor, that pasted its contents in at the top of the file, before `extern "C"` and any similar later additions?...

Mmm... basically, "do what I mean"-ness? Or, well, I think it would be rather confusing _not_ to handle it automatically, since I can see the CUDA-C++ code I've written and...

Wait, really? I thought macros like `load_idx` took the offset into account, and have been writing with that assumption. Should I have been adding `offset` to all my indices?

~~Also, that aside, one of the big advantages of coding in Python - especially Jupyter/IPython, as I am - is the ability to just check your work every couple of...

>That actually bothers me a lot as well, and I have plans for a new API that will make writing and debugging computations easier. But that's a different story. Heh....

Ran into this pothole today. So uh... Any news here?