pixelherodev

Regardless of what syntax is chosen, I think that it is imperative that a solution is chosen. Andrew's comment in the OP is spot-on: as it stands, vectors are a...

I'd go with ``` [-N-]T ``` personally, for the same reasons of consistency I outlined earlier. ``` [*]T pointer-to-many []T slice [N]T array [-N-]T vector ``` vs ``` [*]T pointer-to-many...

That is a good point. However, I think the advantage of consistency is more important, regardless. If I attempt to, say, make a vector of a structure, the compiler will...

Okay, so I've had the stack tracing working in freestanding before in my LIMNOS project. It's broken now though, and I'm not sure if it's due to changes on my...

I'll see about checking code size - I'm requesting the change, it wouldn't be right to take your time on this. For now, I'm more than happy to use my...

I see why LINKABLE should be an option, but why would the first one be a problem? It only affects shared modules *which don't work without this anyways.*

Yeah, one thing I've noticed is that it might be helpful to have a single fips environment for global stuff such as SDKs and fips itself (though not project dependencies...

Ooh! I can actually help with this one! :P If you use DLLEXPORT on functions in the host, and DLLIMPORT them in the plugin, it should work. I have a...

On Linux, nothing is needed, and on OS X, the `-undefined dynamic_lookup` flag is required IIRC.

I don't think so, but I can double check; I'm working on a project utilizing this right now (plugin calling host functions)