dcompute

ch means you can't conditionally insert declarations (i.e. variables, structs/classes, functions). > but beyond the novelty you'd hardly find a mature or reliable codebase written by a team of professionals using hacks like [string manipulation and mixins]. They are a wonderful hack when you need them and nothing else will do what you want. This is not unlike resorting to macros in C++, except that its hygienic, unlike macros. I'm not claiming the project is mature and I'm only one person, but reliable definitely out there. The most heinous set of string mixins i've ever written[1] has definitely got to be the code for generating wrappers to call the OpenCL object property querying functions (clGetDeviceInfo & friends). You need to pass a size and a void pointer to the address of the return object that you have to call once, twice or more (depending on the type of the queried property) to figure out how much memory you need to allocate to call it again. The important thing is that the interface[2] you use to drive this code generation is very clean and return on investment for getting the generic case correct is large. [1]: https://github.com/libmir/dcompute/blob/master/source/dcompu... [2]: https://github.com/libmir/dcompute/blob/master/source/dcompu...