4 ms·
That is equally inscrutable. http://code.kx.com/wsvn/code/kx/kdb%2B/c/c/k.h http://code.kx.com/wsvn/code/kx/kdb%2B/c/c/k.h
by bkeroack 12y ago
That is equally inscrutable.
http://code.kx.com/wsvn/code/kx/kdb%2B/c/c/k.h http://code.kx.com/wsvn/code/kx/kdb%2B/c/c/k.h
- RodgerTheGreat 12y agoPerhaps you should start with a manual instead of C headers: http://web.archive.org/web/20041022042401/http://www.kx.com/technical/documents/kusrlite.pdf http://web.archive.org/web/20041022042401/http://www.kx.com/...
- srpeck 12y agoThis might help you understand it: http://code.kx.com/wiki/Cookbook/InterfacingWithC http://code.kx.com/wiki/Cookbook/InterfacingWithC Once you understand the underlying data structure, a lot of k's design decisions make sense. I am using the k.h file from k4 as almost the sole guide to recreating a toy k5 (http://kparc.com/k.txt http://kparc.com/k.txt) interpreter in C.