-
Eclector
A portable Common Lisp reader that is highly customizable, can recover from errors and can return concrete syntax trees
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
I think this should be safe: https://github.com/phoe/safe-read
This doesn’t provide such functionality out of the box, but it makes it pretty trivial to produce a custom READ that only has the features you want: https://github.com/s-expressionists/Eclector
I think this should be safe: https://github.com/phoe/safe-read
This doesn’t provide such functionality out of the box, but it makes it pretty trivial to produce a custom READ that only has the features you want: https://github.com/s-expressionists/Eclector
I was specifically talking about Common Lisp’s print/read functions which are not safe for untrusted input:
https://github.com/salewski/cl-safe-read/blob/master/README....
Thanks! safe-read and this other one are what I’d seen before: https://github.com/mabragor/cl-secure-read
I’ll look at them more closely.
https://okmij.org/ftp/papers/DDBinding.pdf
I think that you would be able to freeze certain variables in the closure, and have others open eg. API_ENDPOINT variable might be configured to change between environments.
Something like https://github.com/GiacomoCau/wat-js implements delimited continuations, ddbinding and algebraic effects (registered handlers for I/O etc) - pushing continuations over the network should be easier with these facilities.