Lee Taylor

Shroud generates the wrappers from the YAML file. It does not read any source or header files. The YAML file is created by the user by copying declarations into the...

Should this functionality be in the ``sidre/core`` directory, or should we create another directory to add functionality which builds on the core API?

We've talked a lot about building functionality on top of the the core. This is a good example and might encourage more things to be built this way if we...

Thank you for the detailed bug report. I created a branch, cpp-fortran, which adds a test and uses cpp_if for type-bound procedures. Let me know if the code will compile...

I added the use of `cpp_if` in the `typeslib.h` file. I think by conditionally compiling it, it makes it noticeable if it gets accidentally used. I had not considered the...

It looks like that should work if you list the specific types in the `instantiation` field. varargs for function would be more of a problem I think. Fortran supports an...

I added the test on the arraywrapper4 branch. However, I was getting a different error from the Fortran wrapper: Argument 'dshc_rv' of pure function 'c_arraywrapper_get_array_const_bufferify' at (1) must be INTENT(IN)...

I see why the extra Fortran and C files. I made a "fix" recently that allowed ``wrap_fortran=True`` to be set on a single function instead of just at the top,...

We should probably support that, or at least not crash. The issue becomes what if the file you're loading has conflicting attributes? For example, loading an older version of the...

Thanks for the report. I was able to reproduce the problem with your example. It'll be next week before I can start on a fix.