2 ms·
Thank you four your reply. I had my suspicions that might be the issue (the shorthand/differences between gsp/gisp in particular). I also played a bit with the
by e12e 11y ago
Thank you four your reply. I had my suspicions that might be the issue (the shorthand/differences between gsp/gisp in particular). I also played a bit with the simple factorial example[f] from gisp -- which apparently doesn't work with gps(c) (gisp apparently allows calling casts as functions [eg: (int ImNotAnIntButAfloat)] -- looks like gsp chokes on that.
After some tweaking I couldn't get [f] to work with gsp (but it worked fine with gisp + go build). Looks like both projects could use some more (esp. motivating) examples, and maybe a little more introduction/documentation. At least enough to encourage play :-)
[f] https://github.com/jcla1/gisp/blob/master/examples/factorial.gsp https://github.com/jcla1/gisp/blob/master/examples/factorial...
- eatonphil 11y agoGood call with the casting issue. I'd been seeing that that wasn't working correctly but I just now figured it out. Gisp lacked the ability to have function arguments actually be functions themselves. Gsp gets around this by casting __all__ (a lazy move, I know) functions to interface{} then to func([arg core.Any]+) core.Any. I do stop this behavior for a certain whitelist - I need to add int/float64/bool/string to that list I think. This was definitely just a first step. I think getting the Prelude to work is by far the coolest part. It did actually take a lot of trial and error hacking gisp -> gsp to get it working. After this I will probably look into self-hosting documentation and maybe a cookbook.
- e12e 11y agoGood to hear :-) Btw, I'm still not sure what "prelude" means in this context...