ds,
>> Kashyap
>>
>> On Fri, May 15, 2020 at 10:53 PM C K Kashyap wrote:
>>
>>> Absolutely!!!
>>> If that is done - I believe there is no reason not to have pil64 in C
>>> too right :)
>>> Regards,
>>> Kashyap
>>>
>
If that is done - I believe there is no reason not to have pil64 in C too
>> right :)
>> Regards,
>> Kashyap
>>
>> On Fri, May 15, 2020 at 9:55 PM Andras Pahi wrote:
>>
>>> Hi,
>>>
>>> If you are still interested in native/lisp in picolisp32
ely!!!
> If that is done - I believe there is no reason not to have pil64 in C too
> right :)
> Regards,
> Kashyap
>
> On Fri, May 15, 2020 at 9:55 PM Andras Pahi wrote:
>
>> Hi,
>>
>> If you are still interested in native/lisp in picolisp32 then I am
>
Absolutely!!!
If that is done - I believe there is no reason not to have pil64 in C too
right :)
Regards,
Kashyap
On Fri, May 15, 2020 at 9:55 PM Andras Pahi wrote:
> Hi,
>
> If you are still interested in native/lisp in picolisp32 then I am working
> to support the pil64
&
Hi,
If you are still interested in native/lisp in picolisp32 then I am working to
support the pil64
features in picolisp32. The development branch of
https://github.com/pahihu/picoLisp <https://github.com/pahihu/picoLisp>
just missing the coroutines (stay tuned), and builds on 64bit
Got it - thanks Alex.
I wish there was a libposix (perhaps using libuv) that PicoLisp would work
against and then it would magically work on Mac and Windows too :)
I was working on miniPicoLIsp with the idea of building in those
features into miniPicoLisp (since it already works on Windows - buil
On Fri, May 08, 2020 at 06:42:33PM +0200, Alexander Burger wrote:
> Yes, miniPicoLisp and Ersatz do not depend on POSIX. Mini just uses the C
> standard I/O stuff. "POSIX" basically means "Unix".
It means processes (yes, fork()) and process groups, terminal handling, signals,
pipes, file control (
On Fri, May 08, 2020 at 09:28:36AM -0700, C K Kashyap wrote:
> again, miniPicoLisp is also POSIX compliant right - but it uses a very
> narrow slice of the POSIX API. Or am I understanding POSIX wrong here?
Yes, miniPicoLisp and Ersatz do not depend on POSIX. Mini just uses the C
standard I/O stuf
>
>
> How do you mean that? Pil21 is not even finished for the first version.
>
> Perhaps I am remembering it incorrectly - I thought pil21 (a couple of
months ago I think) - did not support 'fork'/'call' etc thereby making me
thing it did not depend POSIX as heavily yet - when I say that I mean,
d
Hi Kashyap,
> If I remember correctly - pil21 initially did not have the POSIX
> requirement. Is there a way to get older versions of pil21 (I know that it
> is a strange request for a POC :) )
How do you mean that? Pil21 is not even finished for the first version.
But anyway it was always POSIX
Thanks Alex,
I think I'll try and see if I can get a simple SDL callback to work with
miniPicoLisp - that way, I can really understand the issues better.
If I remember correctly - pil21 initially did not have the POSIX
requirement. Is there a way to get older versions of pil21 (I know that it
is a
Hi Kashyap,
C K Kashyap writes:
> I am now trying to figure out how to do FFI min miniPicoLisp and I
> realized that only pil64 has native/lisp support. Is there any reason
> it could not be done in the 'c' implementation of pil32? I just wanted
> to make sure that there is no "impossibility" abo
Hi Kashyap,
> I think I have fully digested gen3m.c at this point :). I am now trying to
> figure out how to do FFI min miniPicoLisp and I realized that only pil64
> has native/lisp support. Is there any reason it could not be done in the
> 'c' implementation of pil32?
Pil32 and miniPicoLisp are
Hi Alex,
I think I have fully digested gen3m.c at this point :). I am now trying to
figure out how to do FFI min miniPicoLisp and I realized that only pil64
has native/lisp support. Is there any reason it could not be done in the
'c' implementation of pil32? I just wanted to make sure that there is
14 matches
Mail list logo
