Replace LLVW - Was: Stop using US controlled software stacks!!!
Hi Guido, On Sun, Apr 19, 2020 at 06:41:31PM +0200, Guido Stepken wrote: > But this is not the point. The point is, that MetaCola was a code > generator, where you can implement whole programming languages within just > a few lines of code. > ... > OMeta Parser/Interpreter has been translated into many programming > languages and is used almost everywhere now to implement DSL (Domain > Specific Languages). > ... > 153 Lines of OMeta code: > ... > I almost completely stopped writing code in any programming language by > hand, since there is not a single problem that cannot be solved with OMeta Wonderful! That saves all our problems. No reason to stop pil21 :) LLVM is only needed to translate the IR code, generated from PicoLisp pil21 sources, to the target machine language. You can surely write for us such a translator in 160 lines. For now, targets x86-64, arm64, RISC-V and Verilog on Linux, Android, MacOS and iOS would be enough. Issue closed! :) ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
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 optimized string storage. So, one of the changes I did was to switch to 7 bits for all. So I am trying to alter the code to make it easy for guys like me :) I have a couple of questions 1. About RAM vs ROM. Call me lazy but I would really appreciate a description of how the RAM vs ROM decision is taken here (and in general too..I mean, it is not clear to me how gen3m.c determines how something is never written to or not) if (x > 0) Rom[x] = strdup(buf); else Ram[-x] = strdup(buf); 2. Can I try and make the CELL have an additional byte to store the TYPE and get rid using tagged pointers? Clearly, it would be less efficient at runtime but perhaps it would be more easy to understand. Is there any reason that this would not work? Regards, Kashyap
Why i chose PicoLisp as main language for my projects ...
Hi all! Main argument was, that only with Lisp i can mathematically, formally proof, that my programs *are safe*. Demand for safe programs, libraries of all kinds is going through the roof. Base was this paper here: http://www.cse.chalmers.se/research/group/logic/TypesSS05/Extra/lectnotes_vol1.pdf It has a good reason, why Lisp is also deeply sticking behind Webassembly, the standardized browser container format - and - hopefully - the new upcoming server container format, with S-Expressions at its base: https://developer.mozilla.org/en-US/docs/WebAssembly/Understanding_the_text_format https://github.com/appcypher/awesome-wasm-langs/blob/master/README.md Unbelievable, all that language support, that now is translating to Lisp, isn't it? Pure fun! Formal verifiers - behind the scenes - then will ensure, that everything uploaded (by customers) will precisely follow its predefined specifications isand not doing - by evil code injection - anything other than that! Execution will instantly terminate then. That prototype is finished now, in the testing. And those containers will run on ultra cheap, ultra fast - Lisp executing ASICs with their own TCP/IP stack - in the very short future. Stay tuned. That's why most my software now is implemented in Lisp, most parts in PicoLisp. It's a nice, handy, easy to learn Lisp dialect and libraries are sufficiently complete, nothing important missing. Best of Picolisp is PILOG, the Prolog interpreter that can run on top of a distributed, self replicating, ultra fast persisting database, that comes for free with Picolisp, very much like (or even better) than Closure(Script) with its ultra expensive commercial DATOMIC database. This makes PicoLisp a total killer ... and is coming for free! That's just unbelievable! Nothing else in the world does even come close to that expressiveness and capabilities Even if i am repeating myself: "PicoLisp, in its design, is a genius strike!" And you? What where your motives to switch to PicoLisp? Best regards, Guido Stepken
Re: Stop using US controlled software stacks!!!
Am Sonntag, 19. April 2020 schrieb Tomas Hlavaty : > Hi Guido, > > Guido Stepken writes: >> Using US software stacks, even if open source and under a free license are >> not tolerable. For any nation, for any kind of project. >> >> US Cloud Act, Patriot Act, by law, force US companies as well US >> organisations in general, such as Linux Foundation as well as Apache >> Foundation and LLVM Foundation to comply with US law. > > is using google mail tolerable? I am using US driven services and software libraries/stacks, US computer hardware for unimportant work only. All other neither is internet connected nor does it use any of the known US standards for communication or encryption. I've learned my lessons! ;-) Have fun!
unsubscribe
Good bye Mark Voltz :-( You are now unsubscribed -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: picoLisp 19.12: variable length array in structure fixes
Linux, here Debian GNU/Linux, allows parallel installation of 32/64 bit libraries ... https://wiki.debian.org/Multiarch/HOWTO Sometimes "apt-get install ia32-libs" helps. Have fun! Am Montag, 20. April 2020 schrieb Mike : > April 20, 2020 11:01 AM, "Andras Pahi" wrote: > >> Hi Mike, >> >> pil32, x64 means you’ve built the contents of the src/ dir in x64 mode ? >> > > pil32, x64 - means gcc and voidlinux-x64 compiled-supports multilib. > I use pil32 and pil64 on the same machine, I always in pil64, but can switch fast. > > (mike) > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe >
Re: Stop using US controlled software stacks!!!
Am Sonntag, 19. April 2020 schrieb Tomas Hlavaty : > Guido Stepken writes: >> Picolisp, thanks to Alex' brilliant ideas, behind the scenes, serves as >> prototype of a new kind of "minimalistic, highly efficiency" software >> strategy within the EU. Goal is: Back to the roots, small modules, security >> review everywhere, minimal hardware requirements, driving down energy >> consumption massively. > > does EU fund Picolisp as part of the software strategy? No. I said, that Picolisp ideas serve as prototype for new developments. > If not, why and how could that be achieved? Why should EU fund sponsor something, what's already there? Apart from the fact, that Picolisp not really is unique. But it has plenty of nice ideas in it. > Where can I read about the EU software strategy? We have a EU commission of experts and, of course, the official EU database of sponsored EU projects. E.g. PyPy project has received continuous funding(s). PostgreSQL Columnar Store Extension too. Pharo Smalltalk Environment ... Best regards, Guido Stepken
Re: picoLisp 19.12: variable length array in structure fixes
April 20, 2020 11:01 AM, "Andras Pahi" wrote: > Hi Mike, > > pil32, x64 means you’ve built the contents of the src/ dir in x64 mode ? > pil32, x64 - means gcc and voidlinux-x64 compiled-supports multilib. I use pil32 and pil64 on the same machine, I always in pil64, but can switch fast. (mike) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
unsubscribe
Re: picoLisp 19.12: variable length array in structure fixes
Hi Mike, pil32, x64 means you’ve built the contents of the src/ dir in x64 mode ? Thanks, Andras > There are more numbers for the only task "advent2015": > pil64, x64 - 1 min > pil32, x64 - 9 min > pil32, 686 - 9 min > pil32, 686, -O3 - 7 min > VLA patch, 686 - 10 min > > (mike) > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: picoLisp 19.12: variable length array in structure fixes
> > You don’t need energy, you need some patience. > Hard get patience when code running 9x slower :) Its awesome your patch is working and correct, congratulations! There are more numbers for the only task "advent2015": pil64, x64 - 1 min pil32, x64 - 9 min pil32, 686 - 9 min pil32, 686, -O3 - 7 min VLA patch, 686 - 10 min p.s. I will create patch and will store in tankf33der repo. (mike) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
