Niklas

> > However I also realized now that `platform_config.h` probably isn't an appropriate name anymore. What do you think about renaming it to `product_config.h`? > > The `PRODUCT_` macros are...

yeah, I tried the lsp `hover` function on some stuff and it seems to work everywhere. This has a different approach to the other PR. In the other PR I...

rust-analyzer is technically a compiler, so it requires almost everything that you have in the docker container. The only way to make it work outside the container is to install...

I don't remember exactly, but you need to be able to generate C headers, rust bindings. If you look at the other PR you can see that there are some...

I don't know much about python-c-bindings unfortunately. It seems like CFUNCTYPE cannot desribe `va_list`. So I guess a "generic" callback has to be implemented in C that exposes a callback...

Sorry for the not-so-beatiful code... but something iike below works. I don't know if it is a valid solution for pyepics to depend on an dll though.. libmy_lib.so: ```c #include...

Right, what I want to do is process the exception and not write it to stdout/err. Initially I was going to use [ca_add_exception_event](https://epics.anl.gov/base/R3-14/12-docs/CAref.html#ca_add_exception_event) but pyepics doesn't implement it according to...

> Does sys.stdout.write work OK but not other functions? No, if you do `epics.ca.replace_printf_handler(None)` or `epics.ca.replace_printf_handler(sys.stdout.write)` you get: ``` [ 163. 164. 165. ..., 2208. 2209. 2210.] Traceback (most recent...

Yes I agree, what I actually would like is `ca_add_exception_event`. (The name seems to be misleading, according to the docs it works like something that should have been called `ca_replace_exception_handler`....

> it seems strange to me that using `sys.stderr.write` appears to be ok Are you aware that it would print strings like ` %s: "%s"` to stderr? Is that "ok"...