Re: "macros" in miniPicoLisp

Thanks Alex! On Sat, Mar 2, 2024 at 1:02 PM Alexander Burger wrote: > On Sat, Mar 02, 2024 at 10:05:00AM -0800, C K Kashyap wrote: > > Another installment of the video - > > https://www.youtube.com/watch?v=O52fRAsr7Vg > > Very nice indeed! This is probably the first time Pi

Re: "macros" in miniPicoLisp

t; :) I am finally free to explore my actual ideas now! Regards, Kashyap On Fri, Feb 9, 2024 at 2:28 PM C K Kashyap wrote: > Super! - thank Alex. > > On Fri, Feb 9, 2024 at 11:17 AM Alexander Burger > wrote: > >> Hi Kashyap, >> >> > Does this look lik

Re: "macros" in miniPicoLisp

Super! - thank Alex. On Fri, Feb 9, 2024 at 11:17 AM Alexander Burger wrote: > Hi Kashyap, > > > Does this look like a reasonable way to create the "create-adder" > function? > > > > (de create-adder Args > >(let > > (N (car Args) > > Adder (intern (pack "add-" N)) > >

"macros" in miniPicoLisp

Hi Alex, Does this look like a reasonable way to create the "create-adder" function? (de create-adder Args (let (N (car Args) Adder (intern (pack "add-" N)) P (list 'de Adder '(X) (list '+ N 'X) ) ) (eval P)

Re: miniPicoLisp + libuv +libSDL

Thanks Alex and RCS :) On Thu, Feb 1, 2024 at 10:40 AM Alexander Burger wrote: > On Thu, Feb 01, 2024 at 09:05:17AM -0800, C K Kashyap wrote: > > I finally got around to recording a video (my video recording muscles > have > > atrophied :) ) > > > > https://www.y

Re: miniPicoLisp + libuv +libSDL

I finally got around to recording a video (my video recording muscles have atrophied :) ) https://www.youtube.com/watch?v=Uv0ZiZAfcGc Regards, Kashyap On Fri, Jan 26, 2024 at 8:06 AM C K Kashyap wrote: > Thanks Alex - I'll take the "very good" for now :) > > I think

Re: minipicolisp with big num

:) ... thanks Alex! On Fri, Jan 26, 2024 at 10:37 AM Alexander Burger wrote: > Hi Kashyap, Mike, > > > Hey Mike ... I am actually asking if there is such a port/variation of > > miniPicoLisp that has big num support - just like the regular picoLisp. > > I have never heard of any such version. In

Re: minipicolisp with big num

Hey Mike ... I am actually asking if there is such a port/variation of miniPicoLisp that has big num support - just like the regular picoLisp. Regards, Kashyap On Fri, Jan 26, 2024 at 9:14 AM Mike wrote: > > > > On Jan 26, 2024, at 18:19, C K Kashyap wrote: > > > >

Re: docker for pil21

Nice - I did not know about the --no-cache option :) On Fri, Jan 26, 2024 at 8:09 AM Dmitry Non wrote: > Heya! > Interestingly, I wrote a dockerfile for myself too at the end of Dec.My > versions should be lighter due to the lack of build dependencies in the > final image: > > FROM alpine:3.19 A

minipicolisp with big num

Hey all, Has anyone tried a port of miniPicoLisp with the added big num support? Regards, Kashyap

Re: miniPicoLisp + libuv +libSDL

Thanks Alex - I'll take the "very good" for now :) I think I found a better example for demo - libuv's file change callback .. I'll do a demo using that -> make changes to a picolisp script and the screen gets updated as I save the script :) Regards, Kashyap On Fri, Jan 26, 2024 at 7:48 AM Alexa

Re: miniPicoLisp + libuv +libSDL

ping Alex :) On Wed, Jan 24, 2024 at 7:58 AM C K Kashyap wrote: > Hi Alex et al, > For quite some time now (years), I've been attempting to have a > miniPicoLisp + libSDL + libUV working (on Windows as well) for a while and > I have finally got it working :) ... Much of m

Re: docker for pil21

Nice, Here's some additions to make the image a little lighter (not including the *-dev packages) and also adding the appropriate soft links as indicated in the INSTALL file FROM alpine:latest as builder RUN apk update && apk upgrade RUN apk add bash git make llvm clang readline libffi openssl RU

miniPicoLisp + libuv +libSDL

Hi Alex et al, For quite some time now (years), I've been attempting to have a miniPicoLisp + libSDL + libUV working (on Windows as well) for a while and I have finally got it working :) ... Much of my time was wasted attempting "3 part cell" etc. I thought that I'd record a video of the demo befo

Re: External allocations using miniPicoLisp

Thanks Alex, The penny just dropped for me as I was writing this mail - yup, I remember now :) I think "finally" will do what I need :) Regards, Kashyap On Sat, Dec 2, 2023 at 11:35 PM Alexander Burger wrote: > Hi Kashyap, > > > Is there a reference implementation of external allocation using

External allocations using miniPicoLisp

Hi Alex et al, Is there a reference implementation of external allocation using miniPicoLisp? Here's what I'd like to do - Create a new function called "alloc" that allocates some memory. (let A (alloc 100) (poke A 0 10)) # poke simply writes a byte(10) at offset 0 The part I want to ensu

Re: possible bug in miniPicoLisp?

Got it. Thanks Alex. Regards, Kashyap On Wed, Nov 29, 2023 at 9:57 PM Alexander Burger wrote: > On Wed, Nov 29, 2023 at 08:08:33PM -0800, C K Kashyap wrote: > > Thanks Alex - half a dozen worked in my example :) > > Great :) > > > I completely get the idea of the

Re: possible bug in miniPicoLisp?

Thanks Alex - half a dozen worked in my example :) I completely get the idea of the inefficiency of CELLS=1 - the segfault however seems like a silent bug (more likely some optimistic avoidance of a NULL check somewhere perhaps). What do you think? I say this because, even with CELLS=1, most of t

possible bug in miniPicoLisp?

Hi Alex, I attempted to use 1 as the CELLS value in pico.h and immediately ran into segfault at mark(ApplyArgs); in gc.c. I got around the segfault by simply doing this - if(ApplyArgs)mark(ApplyArgs); if(ApplyBody)mark(ApplyBody); After that, most things work but I ran into another segfault

Re: minipicolisp pointers

> On Sat 21 Oct 2023 at 10:50, C K Kashyap wrote: > > Could I have some pointers on extending MiniPicoLisp to implement > > "call" and external objects? > > not sure what do you mean by "call" and external objects > but https://logand.com/sw/mplisp/files.ht

minipicolisp pointers

Hi all, Could I have some pointers on extending MiniPicoLisp to implement "call" and external objects? My attempt at external object is here - https://github.com/ckkashyap/pl/blob/bcf834075358e21abd4c7ec4adf6862e76df4348/miniPicoLisp/09012023/miniPicoLisp/src/main.c#L764 I am simply looking to avoi

Re: building pilos

> > > > > (using UART for io using --serial stdio option in qemu). The drivers/rest > > of the kernel infrastructure could then be crowd sourced :) > > Will you give it a try? > I think that I am close to doing it with miniPicoLisp :) > You mean Pil64 and PilOS? (Beause pil21 has no assembly so

Re: building pilos

you have already answered this but, does it make sense to have a different extension for the assembly files? Technically, I don't believe that they are plicolisp sources right? Regards, Kashyap On Thu, Oct 5, 2023 at 8:03 AM Alexander Burger wrote: > On Thu, Oct 05, 2023 at 07:32:26AM -0

Re: building pilos

Thanks Alex, Any chance that we could expect a pil21 based pilos? I had not been watching pil21 for a while - I looked at it now and I really liked "lib.c" :) If I understood right, then all the platform dependencies are in there (atleast as far as the picolisp executable) On Thu, Oct 5, 2023

Re: pilog on minipicolisp

Thanks Alex! Once I included lib/pilog.l, the example friends.l at https://picolisp-explored.com/learning-pilog-2-facts-rules-queries?source=more_series_bottom_blogs worked! I had to comment out the section below "# Basic Rules" though - even (be repeat) simply causes a segfault. Regards, Kashya

building pilos

Hey Alex, It looks like pilos build may be broken :( I think it has dependency on pil64. I will take a look more later but it would be great if you could share the updated instructions :) Regards, Kashyap

pilog on minipicolisp

Hey Alex et al, It looks like the pilog support in minipicolisp is perhaps different from picolisp. Am I missing something? The "diff" file does not really call out anything. kashyap@DESKTOP-NICP8CC:~/s/embeddedpicolisp/miniPicoLisp/src$ ../pil : (be age (Paul 19) ) !? (clause CL) clause -- Unde

Re: Question about get/put REPL vs executing a file

Got it - I'll just use non-transient symbols like 'A instead :) Thanks Alex! Kashyap On Sat, Sep 23, 2023 at 12:02 PM Alexander Burger wrote: > Hi Kashyap, > > > kashyap@CPC-ckk-S75640M:~$ cat a.l > > (de add (N D) > >(put 'STORE N D) ) > > (add "A" 10) > > (add "B" 20) > > (prinl (get 'STO

Question about get/put REPL vs executing a file

Hi Alex et al, Following illustrates the inconsistent behaviour of get/put between file and REPL. kashyap@CPC-ckk-S75640M:~$ cat a.l (de add (N D) (put 'STORE N D) ) (add "A" 10) (add "B" 20) (prinl (get 'STORE "A")) (prinl (get 'STORE "B")) kashyap@CPC-ckk-S75640M:~$ pil a.l 10 20 : (get 'STOR

Re: Question about , in the tweet

Got it ... I had done a quick check last night to validate and I had the wrong observation because "Language" was already set by the call with the "," so it appeared to work without the comma :) Regards, Kashyap On Thu, Jun 30, 2022 at 6:39 AM Alexander Burger wrote: > Hi Kashyap, > > > I belie

Question about , in the tweet

Hey Alex, I believe that the comma was not strictly necessary in this tweet https://twitter.com/PicoLispREPL/status/1542382434066788352 - the one before "Language". Is that correct? Regards, Kashyap

Re: PicoLisp REPL on Twitter

Very cool ... although the subject line made me think of something else :) - you tweet a picolisp expression and it replies with the evaluation!!! On Tue, Apr 19, 2022 at 6:25 AM pd wrote: > Nice! > > On Tue, Apr 19, 2022 at 7:36 AM Alexander Burger > wrote: > >> Hi all, >> >> I started a new T

Re: An assembly question from the past

0386/80486/80586 'bare metal' > (or at least 'bare VM') -- talking directly to a HW serial port and reading > from a FAT file system? > > -Original Message- > From: > Sent: Mar 30, 2022 10:38 AM > To: > Subject: Re: An assembly question from the pa

Re: An assembly question from the past

> Good, but isn't miniPicoLisp plan vanilla C anyway? I think it uses only > stdio > library functions. > Thanks :Alex :) ... almost Vanilla C I think - with some gcc toppings (VLA particularly) ;) I also moved away from pointer tagging in favor of an extra "part" in the cell. This takes away any

Re: An assembly question from the past

Thanks for the clear explanation Alex, Just to give some background - I've been working on the attempt to port miniPicoLisp to windows (more like making vanilla C as the only dependency). I wanted to make sure that I understood the cost of not going with assembly. Since I use https://github.com/lib

Re: An assembly question from the past

Thank you Alex, I can see how you would have to end up writing the whole thing in assembly - in the example you shared. Would it be right to say that its only the carry flag that you need or is it just an example and there are other flags too? Can I say that the need is restricted to the use of Big

An assembly question from the past

Hey Alex, I had reached out to you about the need for assembly in the past and you had mentioned the following - > 'c' implementation of pil32? >> Pil32 and miniPicoLisp are written in C, and C does not support calling >> other functions in a generic way. This is one of the reasons pil64 was

Re: 3 part cell miniPicoLisp

Hi all, I've dropped the idea of libuv for now. I have however got unlimited string back and also unlimited big num support (using libtommath <https://www.libtom.net/LibTomMath/>) Regards, Kashyap On Thu, Dec 31, 2020 at 11:52 AM C K Kashyap wrote: > Hi All, > I had b

Re: Clarifications about evExpr

Got it! ... thank you so much Alex! The (X Y . Z) and the @ scenarios fill the gap in my understanding! Regards, Kashyap On Wed, Oct 13, 2021 at 7:11 AM Alexander Burger wrote: > Hi Kashyap, > > > I was going over the evExpr functions in miniPicoLisp/PicoLisp 32 and > had a > > couple of questio

Clarifications about evExpr

Hi Alex, I was going over the evExpr functions in miniPicoLisp/PicoLisp 32 and had a couple of questions - If I understand correctly - if (isNil(y)) block deals with expressions such as (F 1 2) where F => (de F (X Y) (+ X Y)) and the else if (y != At) block deals with the scenario where F => (de

Re: Big int in picolisp

Thanks Alex, Regards, Kashyap On Sun, May 16, 2021 at 10:08 PM Alexander Burger wrote: > Hi Kashyap, > > > I am trying to understand how big integers are stored in Picolisp. I > notice > > that the ASCII values of the digits are stored in some cases - for > example > > 1234 is stored as 0x343332

Big int in picolisp

Hi Alex, I am trying to understand how big integers are stored in Picolisp. I notice that the ASCII values of the digits are stored in some cases - for example 1234 is stored as 0x34333231. That does not look like the format that's used always - I am going by the "> 9" references in the cod

Unsubscribe

Šo'¤“*-¢ç!r‰˜¢æ«zz0º{.nÇ+‰· 发自我的小米手机

Re: Question about the "next ptr" in heapAlloc

Got it ... makes sense ... thanks Alex :) Regards, Kashyap On Tue, Mar 2, 2021 at 10:04 PM Alexander Burger wrote: > Hi Kashyap, > > > I noticed that in the linked list of free cells, "car" is used as the > next > > pointer. Is the choice arbitrary? I could've been "cdr" too right? Just > > curi

Question about the "next ptr" in heapAlloc

Hi Alex, I noticed that in the linked list of free cells, "car" is used as the next pointer. Is the choice arbitrary? I could've been "cdr" too right? Just curious if there is some interesting reason behind it :) Regards, Kashyap

Re: Picolisp Outlook

I also believe that the simplicity of PicoLisp by itself is a "killer app". I've explored several languages in the past but PicoLisp is the only one that allowed me to understand the implementation of the language all the way (I still have to work on the external symbol bit :) . I was so used to se

Re: native/lisp in picoLisp 32

, 2021 7:29 AM, "C K Kashyap" wrote: > > > > > Hi all, > > > Has anyone done the C implementation of the native and lisp (for > callback)? I am trying to work it > > > out based on the 64bit source but I think it will be a lot easier if I > had a C

native/lisp in picoLisp 32

Hi all, Has anyone done the C implementation of the native and lisp (for callback)? I am trying to work it out based on the 64bit source but I think it will be a lot easier if I had a C implementation for reference :) Regards, Kashyap

3 part cell miniPicoLisp

Hi All, I had been exploring the miniPicoLisp source for several months now. My goal was to make it compile with Microsoft C compiler and Tiny C Compiler ( TCC ) on windows - and gain a deeper understanding of the implementation in the process. In

Re: PicoLisp Chess

Merry Christmas to you too Alex! Merry Christmas to the picolisp family!!! Regards, Kashyap On Thu, Dec 24, 2020 at 7:02 AM Alexander Burger wrote: > Hi all, > > I should announce the new version of PicoLisp Chess here too. > > Not that it is a strong chess program (not at all!), but it has some

Re: Array avoidance example

Got it! makes sense. Thanks a lot Alex and Alex :) On Fri, Nov 13, 2020 at 9:30 AM Alexander Burger wrote: > Hi all, > > On Fri, Nov 13, 2020 at 06:05:11PM +0100, Alexander Shendi wrote: > > I'm the wrong Alex (and I'm probably wrong), > > You are not wrong (in any case ;) > > > > but I would th

Re: Array avoidance example

Thanks Alex, Is the allocated memory purged by the GC in your example? If not, would it be straightforward to plug it in a manner that the GC handles the free? Regards, Kashyap On Thu, Nov 12, 2020 at 11:21 PM Alexander Burger wrote: > Hi Kashyap, > > > Could you please share the example where y

Array avoidance example

Hi Alex, Could you please share the example where you shared how native code interface could be used to malloc a section of the heap? I believe you shared this in the last PiCon. Regards, Kashyap

Re: PilCon Friday

ource of problems was that the ServerEvent facility > that Olaf was using only sends a single line at time to the other side. > > Olaf's motto for the evening: "when you read the picolisp documentation, > you have to read every word" > > There may have a been a few o

Re: PilCon Friday

As bad an excuse that it may sound, it is the truth - I messed up my alarm setting (AM vs PM) :) and missed the meeting. Could I request someone to please summarize what was discussed? particularly about the "interpreter only" approach. If it was not discussed then perhaps I can request Alex to wr

Re: PilCon Friday

While at it, it would be good to touch on the "interpreter only" approach of PicoLisp. It is objectively simpler than an interpreter AND compiler implementation. However, I would love for some expansion on the explanation of "True equivalence of code and data". Also, is there any update to the view

Re: A question about the definition of tail in miniPicoLisp

preter model on the C side, you just > change the cast operation from a no-op to an actual conversion. The > rest of the picoLisp word manipulation system remains untouched, > keeping the pointer adjustment concept and the homogeneous heap. > > AlexG > > > On 27/08/2020,

Re: A question about the definition of tail in miniPicoLisp

Thanks Alex, About why I am trying it - it's primarily just a learning exercise for me. What I am trying is expanding the cell to 4 words instead of two and use the extra words as the meta data and not require tagged pointers. This way I could even build it with TCC that does not seem to align func

A question about the definition of tail in miniPicoLisp

Hi Alex, I am still working on the idea of using non-tagged pointers in miniPicoLisp - in order to get rid of the requirement that function pointers be word aligned. In the process I noticed that the definition of tail is as follows - #define tail(x) (((x)-1)->cdr) Does this not result in

Re: Question about miniPicoLisp

Thanks Alex! On Thu, Aug 20, 2020 at 11:02 PM Alexander Burger wrote: > Hi Kashyap, > > > init.s defines append as follows - > > append {doAppend} > > ,NIL @X @X)) (((@A . @X) @Y (@A . @Z)) (append @X @Y @Z))) . T) > > > > I gather that the second line that starts with ',' adds properties to

Question about miniPicoLisp

Hi Alex, init.s defines append as follows - append {doAppend} ,NIL @X @X)) (((@A . @X) @Y (@A . @Z)) (append @X @Y @Z))) . T) I gather that the second line that starts with ',' adds properties to the symbol. It is not clear to me what the properties are for. Can you please throw some light on

Re: Fridays for Functions (Was: PilCon 2020)

Thu, Jul 2, 2020 at 12:06 PM C K Kashyap wrote: > >> I can't wait :) >> >> On Thu, Jul 2, 2020 at 9:46 AM Alexander Burger > > wrote: >> >>> On Thu, Jul 02, 2020 at 09:28:09AM -0700, C K Kashyap wrote: >>> > Just to confirm - is this at 8

Re: Fridays for Functions (Was: PilCon 2020)

I can't wait :) On Thu, Jul 2, 2020 at 9:46 AM Alexander Burger wrote: > On Thu, Jul 02, 2020 at 09:28:09AM -0700, C K Kashyap wrote: > > Just to confirm - is this at 8am UTC on 3rd July? > > Yes, that's right. About 15 hours and 20 minutes from now ;) > &g

Re: Fridays for Functions (Was: PilCon 2020)

Just to confirm - is this at 8am UTC on 3rd July? regards, Kashyap On Wed, Jul 1, 2020 at 8:42 AM C K Kashyap wrote: > Yes, I agree. I am totally onboard with "meet and greet" ... It will be > good to just interact with folks with similar interests! > > Regards, >

Re: Fridays for Functions (Was: PilCon 2020)

Yes, I agree. I am totally onboard with "meet and greet" ... It will be good to just interact with folks with similar interests! Regards, Kashyap On Wed, Jul 1, 2020 at 7:48 AM Alexander Burger wrote: > Hi Kashyap, > > > Would this be recorded? There is just not enough picoLisp video content

Re: Fridays for Functions (Was: PilCon 2020)

Would this be recorded? There is just not enough picoLisp video content out there in my opinion. I would like a session on History/evolution of Picolisp in your own words Alex! Regards, Kashyap On Wed, Jul 1, 2020 at 3:59 AM Alexander Burger wrote: > Hi all, > > On Thu, Jun 18, 2020 at 08

Re: Fridays for Functions (Was: PilCon 2020)

+ 1 ... looking forward to it On Wed, Jun 17, 2020 at 11:48 PM Alexander Burger wrote: > Hi all, > > On Wed, Jun 03, 2020 at 07:54:22AM +0200, Alexander Burger wrote: > > I would propose informal Jitsi meetings every second Friday or so. The > time > > could be alternating 8:00 and 16:00 UTC

Re: cells in picolisp [tutorial, slides]

I liked it :) Thanks, Kashyap On Fri, Jun 5, 2020 at 5:37 AM Mike wrote: > hi all, > > https://envs.net/~mpech/cells-tutorial.pdf > > I've created tutorial about cell as root of data type hierarchy. > Goal of PDF is understanding of destructive functions. > I hope you will learn something new. >

Re: Fridays for Functions (Was: PilCon 2020)

%2Cproduct%2Ccomponent%2Cpriority%2Cassigned_to%2Ccf_status_firefox75%2Ccf_status_firefox76%2Ccf_status_firefox77%2Ccf_status_firefox_esr68%2Cbug_status%2Cresolution%2Cchangeddate&query_format=advanced&status_whiteboard=jitsi-meet&status_whiteboard_type=substring&query_based_on= > >

Re: Fridays for Functions (Was: PilCon 2020)

Is Jitsi a phone only tool? I only see an apple/android download here - https://jitsi.org/#download Regards, Kashyap On Wed, Jun 3, 2020 at 7:55 AM C K Kashyap wrote: > Wonderful idea indeed! > > On Wed, Jun 3, 2020 at 6:01 AM Davide BERTOLOTTO < > davide.bertolo...@g

Re: Fridays for Functions (Was: PilCon 2020)

Wonderful idea indeed! On Wed, Jun 3, 2020 at 6:01 AM Davide BERTOLOTTO < davide.bertolo...@gmail.com> wrote: > Wonderful idea > > On Wed, Jun 3, 2020, 13:27 O.Hamann wrote: > >> ++ >> >> On 03.06.20 07:54, Alexander Burger wrote: >> > I would propose informal Jitsi meetings every second Friday

Re: Native callbacks in PicoLisp

Thanks for the clarification Alex! ... I am not a fan of threads - just wanted to confirm. Regards, Kashyap On Fri, May 22, 2020 at 9:58 PM Alexander Burger wrote: > Hi Kashyap, > > > In the section about callbacks ( > > https://software-lab.de/doc/native.html#funptr) it is not explicitly > > me

MiniPicoLisp with SDL on GNU/Linux, Mac, Windows

Hi all, It is super cool to see SDL graphs driven through miniPicoLIsp :) ... I am too excited and wanted to share it before doing some polishing https://github.com/ckkashyap/MiniPicoLisp/tree/SDL This code builds and runs on "all" the operating systems :) My next goal is integrate it with o

Native callbacks in PicoLisp

Hi Alex et al, In the section about callbacks ( https://software-lab.de/doc/native.html#funptr) it is not explicitly mentioned that the callback (lisp ...) cannot be called from a different thread. However, since PicoLisp does not have threads, I'd imagine that callbacks cannot be called from a d

Re: picoLisp 19.12: variable length array in structure fixes

Super ...Congratulations Andras! I just gave it a spin and it just worked. I generated 64bit and 32bit executables (after installing libffi-dev and libffi-dev:i386) and tried (call "ls") :) I am particularly happy since I will be able to reference C code for the FFI implementation that I could

Re: native/lisp in picolisp32

usually the "host" by design - but I wonder > whether, if you avoid that and try to make miniPicoLisp the conceptually > freestanding language, you'd end up erasing most of what makes it distinct > from the main picoLisp anyway. > > AlexG > > On Sat, 16 May 2020,

Re: native/lisp in picolisp32

Oh btw Andras, The main reason I would love those features in pil32 (C) is so that I can more easily translate it to miniPicoLisp. I really want to be able to have a system that requires nothing more than C :) Regards, Kashyap On Fri, May 15, 2020 at 10:53 PM C K Kashyap wrote: > Absolut

Re: native/lisp in picolisp32

gt; features in picolisp32. The development branch of > https://github.com/pahihu/picoLisp > just missing the coroutines (stay tuned), and builds on 64bit/32bit > targets. > It uses libffi for the native C calls. > > Regards, > Andras > > On 2020. May 8., at 16:36, C K Kashyap

Re: native/lisp in picolisp32

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

Re: native/lisp in picolisp32

> > > 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

Re: native/lisp in picolisp32

is a strange request for a POC :) ) Thanks Tomas for your ffi link. Regards, Kashyap On Fri, May 8, 2020 at 2:24 AM Tomas Hlavaty wrote: > Hi Kashyap, > > C K Kashyap writes: > > I am now trying to figure out how to do FFI min miniPicoLisp and I > > realized that only pil

native/lisp in picolisp32

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

Re: miniPicoLisp cons(Nil, Nil);

Oh yes thanks Alex, Regards, Kashyap On Sat, May 2, 2020 at 7:10 AM Alexander Burger wrote: > Hi Kashyap, > > > Could you please tell me why we have the cons(Nil, Nil); in gen3m.c right > > after insert(&Intern, "NIL", romSym("NIL", "(Rom+1)")); ? > > This allocates a dummy cell, required by

miniPicoLisp cons(Nil, Nil);

Hi Alex, Could you please tell me why we have the cons(Nil, Nil); in gen3m.c right after insert(&Intern, "NIL", romSym("NIL", "(Rom+1)")); ? Regards, Kashyap

Re: Pil21 Status

Congratulations Alex On Fri, May 1, 2020 at 1:06 PM cilz wrote: > Congrats! Thank you very much for your hard work. PicoLisp has been my > best friend during this quarantine :) Best, Eric > > Le 01/05/2020 à 15:41, Alexander Burger a écrit : > > Hi all, > > > > pil21 reached the first milest

Re: PilCon 2020

+1 for online :) On Wed, Apr 22, 2020 at 4:48 AM David Bloom wrote: > +1 lurker interested in an online conference. While it is disappointing to > not be able to meet people in person it seems that attendance will be > dramatically increased. Happy to help with testing online tools if needed. >

Re: MiniPicolisp Questions

nd perhaps help with the appreciation for the tagged pointer as an optimization. But yes, I can clearly see that a 9byte cell is not a good idea :) On Wed, Apr 22, 2020 at 8:27 AM C K Kashyap wrote: > Got it. The idea was not to encode more types - just reduce the > "complexity" of

Re: MiniPicolisp Questions

Got it. The idea was not to encode more types - just reduce the "complexity" of tagged pointers and impose the word aligned function address restriction but from what I gather. Yes, a separate byte heap would totally be much ore complex. One of the reasons of this desire was to build miniPicoLis wi

Re: MiniPicolisp Questions

Hi Alex, Quick question - when you mentioned "doubling of space" - perhaps you were talking about systems that can only have WORD aligned pointers - is that correct? Regards, Kashyap On Wed, Apr 22, 2020 at 6:56 AM Guido Stepken wrote: > Well, we have year 2020, not Dijksra 1978. Even embedded

Re: MiniPicolisp Questions

Thanks Alex, I was thinking of increased memory space - not exactly doubling - I was thinking it would just be one additional byte per CELL. Ofcourse this additional byte would not have the same lifetime of the CELL so it should not need any extra management. I feel encouraged - I'll give it a tr

Re: MiniPicolisp Questions

Thanks Alex, Yup, I can see what's going on now about RAM vs ROM :) About the the CELL having an additional byte, I meant that the CELL size would be 2*WORD + 1... that should work too right? I would not need any masking in that case. Regards, Kashyap On Mon, Apr 20, 2020 at 11:06 PM Alexander

MiniPicolisp Questions

Hi Alex et al, I've been working on miniPicoLisp source with the idea of making it more easy to understand - granted, it's really simple but it's simplicity may not be apparent from looking at the source to some (such as myself). For instance, it took me some time to get what's going on with the op

Re: Tiny C Compiler

ARM > NEON). It's a GCC thing, not a C standard! ;-) > > https://stackoverflow.com/questions/7895869/cross-platform-alignx-macro > > Hope, that helps. > > Am Montag, 13. April 2020 schrieb C K Kashyap : > > Hi all, > > I just noticed that TCC was mentioned in another

Tiny C Compiler

Hi all, I just noticed that TCC was mentioned in another thread so I wanted to share my experience with it. I had tried to build miniPicoLisp with it but unfortunately, TCC does not seem to generate aligned functions :( it did not seem to honor __attribute__((aligned)) Does anyone else have any e

Re: Lisp, a language for "Stratified Design" Podcast and paper.pdf

Thanks for sharing ... loved the podcast! Regards, Kashyap On Fri, Apr 10, 2020 at 2:28 PM Guido Stepken wrote: > A highly inspiring, philosophical Podcast about Abstractions in Lisp, that > - until today - you simply can't do in other programming languages: > > https://podcasts.google.com/?q=Li

Re: 64bit miniPicoLisp

Got it. Thanks Alex. Regards, Kashyap On Thu, Apr 9, 2020 at 10:14 PM Alexander Burger wrote: > On Thu, Apr 09, 2020 at 09:46:05PM -0700, C K Kashyap wrote: > > gcc. Things work fine when I use gcc 7.5 or above on Linux. However, > when I > > use gcc 6.3, I find that some of t

Re: miniPicoLisp/picoLisp difference

I just noticed that all the picolisp emails were going into my spam folder!!! Thanks Alex -- phew - I thought I had messed up something! On Thu, Apr 9, 2020 at 10:02 PM Alexander Burger wrote: > Hi Kashyap, > > > (let (A 1 (B . C) (2 3)) B) -> 2 > > > > where as in miniPicoLisp (compiled using

64bit miniPicoLisp

Hi Alex, I am running into a weird situation when I build miniPicoLisp with 64 bit gcc. Things work fine when I use gcc 7.5 or above on Linux. However, when I use gcc 6.3, I find that some of the symbols are not found. I have not dug into this much but I was wondering if there is any advice on the

miniPicoLisp/picoLisp difference

Hi Alex, I noticed that in picoLisp the following is true (let (A 1 (B . C) (2 3)) B) -> 2 where as in miniPicoLisp (compiled using gcc 7.5 on ubuntu with -m32 added to gcc in the Makefile) I get NIL for the same expression. Is that expected? Regards, Kashyap

minipicolisp with Microsoft C compiler

[Sorry if this message messes up your thread - something went wrong with my email and my sent emails got deleted] I just realized that picolisp source has tests and I am going to try and find out how many of them are valid for miniPicoLisp. If someone knows of a better way to get the tests for min

  1   2   3   4   >