James Craig Burley

This commit seems to have completely eliminated all crashes, though they seemed to go away earlier, as I was experiencing some confusion while getting used to how building and installing...

FWIW, I wrote a Wiki page on my performance analysis here: https://github.com/jcburley/LispZeroGo/wiki/Performance-of-LispZeroGo-vs-LispZero-(C) Enjoy, and thanks again for all the help!

Also note the new issue I created on eliminating casting-only `map`, which is likely only a performance, not correctness, issue: https://github.com/elliotchance/c2go/issues/795

FYI, I just now noticed that postincrement in a `while` seems to be handled properly: ``` while (i--) { ``` This becomes: ``` for func() int32 { defer func() {...

A little debugging later and I found this workaround helps **c2go** run to completion: https://github.com/jcburley/LispZero/commit/283d015ead46ea3f6df890b63bbd7a81fec6c22d (I'm new to Go, dlv, etc., so it took me a little while to find...

**c4go** does not crash on this tiny test case: ``` typedef struct { int a; int b; } *twoints; ``` (**c2go** currently does.) **c4go** generates this from that test case:...

Do you think the **c2go** transpilation of the same code (shown above) is wrong, even though it compiles and seems to run okay? (It looks okay to me, but I'm...

(Did you mean "May be error on (376) is **im**possible to solve, by the way?)

Hm, I don't see those warnings at the top of my (current) **lisp-zero-single.go** file. I have other tests that allocate **VMpeak** as high as **3.8G** yet seem to run to...

Adding another level of indirection (and removing the outer function while defining `get_p`, to avoid that other issue) shows the symptoms a little more clearly: ``` struct cw_s { char...