Hello Alex Gilding :-)
You are now subscribed
May I?
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
pposed to
some custom dialect nobody knows how to use. (Speaking of which, are we
permitted to redistribute the documentation?)
Thanks,
Alex Gilding
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi,
1) Is there a definitive list somewhere of which features are
present in the different versions of PicoLisp?
Well, you can generate it easily ;-)
: (diff (all) (in '("mini/pil" "-println (all)" -bye) (read)))
Haha, that answers that easily enough! Thanks for pointing it out. I'd
better re
rger wrote:
Hi Tomas,
Alex Gilding writes:
Is there any kind of established definition of what specifically
constitutes the PicoLisp language? i.e. what must, and what should, a
third party Lisp implementation provide in order to be able to call
itself a PicoLisp?
...
The only definition
(If you can forgive a PicoLisp n00b shoving his face into the discussion...)
You actually have that the opposite way around. Tail call elimination
(tail recursion is just one special case of tail calls) is a *semantic*
rule that says that a function's activation no longer has any influence
on
On 10/05/2013 16:19, Alexander Burger wrote:
you cannot do TCE while interpreting List structures. You have to do
it in the compiler, as it requires some analysis of the code structure.
One could always look ahead and try to analyse the s-expression's
structure while executing it... this proba
Sadly not PicoLisp, but another alternative you could look at if you need a
really, *really* tiny Lisp is PICOBIT: https://github.com/stamourv/picobit
It's a Scheme. Claims (perhaps pinch of salt needed) to be able to run in as
little as 1KB RAM. The original developer was the guy behind Gambi
> 2) I suppose that the garbage collector would have to keep track of
> all those CELL pointers in the array, that are outside of the reach of
> the picolisp symbol table. That would be the price to pay, I think
> a smaller price than adding another datatype.
>
>
One cheap workaround for this would
On 8 March 2015 at 13:52, Lawrence Bottorff wrote:
> Does the Lisp world, specifically picoLisp, have a response to these
> insistent "Besserwisser" people?
>
I sincerely hope not.
Please don't turn this into a tribal thing. This is the sort of reasoning
that led to the CL community's terrifyin
I get the impression comparing CL to Picolisp is a bit like comparing C++
to Javascript* - they look similar only if you stand far enough away from
the screen...
(* there isn't really a C-family language that fits the example, but anyway)
On 8 June 2016 at 14:46, Joe Golden wrote:
> I've writte
With a system like miniPicoLisp, like any ultra-light footprint interpreter
- does a general purpose FFI really gel with the design?
IMO the way people normally use interpreters in this weight class (see
also, Lua, Chibi, picoC, Jim, ...) is to embed them: i.e. the interpreter
becomes a first-clas
One technique in C for mapping incompatible pointer or alignment sizes
(for when you can't, or don't want to, convert directly between
pointer and `intptr_t`) is to use an intermediate array, and instead
of storing native pointers, store indexes into this array.
For your case you could put all the
14 matches
Mail list logo
