<abu[m]>
on 14 it builds the non-opaque sources too
<tankf33der>
asap, getting llvm13 ecosystem
<abu[m]>
cool
<abu[m]>
Does pb1n preserve TABs? (i.e. in Makefile)
<abu[m]>
Anyway you know what it is. I made two globals OPT and OPQ to switch between old and new
<abu[m]>
And -O3 needs to be off, otherwise 'opt' crashes with a segfault in llvm14
<tankf33der>
i used opaque flag in clang too
<tankf33der>
how it compiled without it?!
<abu[m]>
No sources are changed yet
<abu[m]>
And clang is irrelevant for us. It is used only to compile .c files or assemble .s files. The pointer stuff is in the stage .l -> .ll -> .bc
<tankf33der>
clang used to compile lib.c
<tankf33der>
all three must be on the same level of opaquness
<tankf33der>
opt, llvm-link and clang
<abu[m]>
ok, but on 14 nobody complained
<tankf33der>
ok
alexshendi has joined #picolisp
seninha has quit [Quit: Leaving]
seninha has joined #picolisp
fuxoft has joined #picolisp
fuxoft has quit [Client Quit]
fuxoft has joined #picolisp
<fuxoft>
Sorry for the noob question but in the PicoLisp reference documentation, why do some of the definitions contain dot (e.g. "(de sym . any) -> sym") and others do not (e.g. "(diff 'lst1 'lst2) -> lst")? In both cases, I use these commands without entering the dots. Does this have something to do with dotted pairs?
<abu[m]>
Yes, correct
<abu[m]>
(de f (N) (foo N)) is the same as (de f . ((N) (foo N)))
<abu[m]>
so 'any' is a function here
<abu[m]>
Try to draw these expressions in box notation
<fuxoft>
OK I'll try, Thanks for pointing me in the right direction