Steffen Müller

Okay, I made this work in a branch. Please see the commit message. This is proof of principle only. https://github.com/tsee/C-Blocks/tree/tsee/nasty_automatic_xs_hack

Sorry for the slowness - life's been busy. My initial response was going to be "I have concerns about the types for this being global due to being Perl namespaces"....

Hmm. Before I comment further, I'll do some more "have you seen this" showing off. ;) I think you might find some other prior art on this somewhat interesting. You've...

Forgot one bit of commentary: A variation on the hints hash trick could be to use it to store `$^H{"C::Blocks/types"} = $id` and then use `$id` to look up a...

Regarding the reading: Apologies if that sounded patronizing. Not meant that way at all! You just seem to be into that sort of curious stuff, so I figured I'd share....

I thought a bit more about the "one SV magically gets transformed to several C types/variables" use case. Essentially, with the current conceptual approach (including the {typeA varA, typeB varB,...

Can't wait to hear about it! (Or read the code.)

So this changes significantly due to: ``` ##################### # executable_screen # ##################### # Given a list of identifiers, puts all of them in a C file and # processes the...

Personal nit: I'd stay away from IO::Prompter and anything fancy like that. In particular, any user interaction at Build.PL/configure time needs to automatically degrade to "just choose defaults" or "don't...

I don't understand the code here very well, but indeed I was assuming that since its purpose is to try and compile things and it bombs if it doesn't find...