Hello Andras Pahi :-)
You are now subscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hello,
If you are interested I have patched the 19.12 32bit sources to compile without
GCC.
I have attached the changed files: pico.h, main.c, apply.c and flow.c
Since clang does not support variable length array in structures I allocate the
bindFrame
with alloca() and provided a macro in pico
Hi Andras,
> If you are interested I have patched the 19.12 32bit sources to compile
> without GCC.
> I have attached the changed files: pico.h, main.c, apply.c and flow.c
Thanks a lot!
> Since clang does not support variable length array in structures I allocate
> the bindFrame
> with alloca
Hi Alex!
"completely replace it with pil21" ... (LLVM based)
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
Hello,
with your patches, I've compiled Picolisp on 32-bit Termux + Clang without
any problems.
Thanks a lot! Great job!
Greetings
Alfonso V.
Andras Pahi schrieb am Sa., 18. Apr. 2020, 20:00:
> Hello,
>
> If you are interested I have patched the 19.12 32bit sources to compile
> without GCC.
>
Hey Guido!
While I don't disagree with you in spirit (and I'm sure it's the same
for most of our community, we're a bunch of purist radicals), I have to
disagree with your tone.
> And i can assure you: My influence is **much bigger** than you might
> think! Stop that, immediately!
This is childi
Just for fun: I cannot imagine Guido's email what if Alex will announce
that he will stop pil21 and decide to port PicoLisp to WINDOWS and use .NET
as official VM ^^
On Sun, Apr 19, 2020 at 7:24 AM wrote:
> Hey Guido!
>
> While I don't disagree with you in spirit (and I'm sure it's the same fo
Hi Guido,
> Using US software stacks, even if open source and under a free license are
> not tolerable. For any nation, for any kind of project.
Then no software stack, from anywhere, is tolerable.
In case of pil21, where is the problem? I use Lisp to generate LLVM-IR, then the
llvm assembler to
