lispbub

Hi there, I would suggest following approach for the compute shader: ``` (simple-print (progn (comment (format nil "#version 430 core~%") :prefix "") (decl (((layout (local-size-x 32) (local-size-y 32)) in nil...

Now we have an additional generator: oclgen. Currently it's just a prototype which adds some basic qualifiers but I'm in the midst of adding more ocl elements. Now the example...

Is it really necessary to run a different generator for subforms? Can't we simply derive oclgen from cugen? By the way oclgen is derived from cxxgen. And the vector-initialization: `(decl...

seems legit, if you often use it :) but can't you simply place the ``(load "file")`` directly in the source file?

@kiselgra You simply want an optional 'docstring-slot' for statement-nodes?

Now i get it. You want such doc-strings to be converted to comments in C. The only benefit I see is the more lisp-like notation, but is there another good...

You've got a point there. I will add such a functionality :)

The syntax is slightly different: (Also there was a small bug in the code, but it should work now) ``` (function foo () -> (inline (__attribute__ always_inline) int) (return 0))...

Support for new command ``attribute`` since e9a5aed44dbcab97465543d6714c922efa0dd4f3 ``` (function foo () -> (inline (attribute always_inline) int) (return 0)) ``` yields: ``` inline __attribute__ ((always_inline)) int foo() { return 0; }...

It's now possible to disable the line break in comments with: ``` (function foo () -> (inline (comment "__attribute__((always_inline))" :prefix "" :linebreak nil) int) (return 0)) ``` allowing easy workarounds:...