clacke[m] has quit [Read error: Connection reset by peer]
clacke[m] has joined #picolisp
pchrist has quit [Ping timeout: 276 seconds]
pchrist has joined #picolisp
orivej has joined #picolisp
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #picolisp
aw- has joined #picolisp
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #picolisp
chuckJ has joined #picolisp
chuckJ has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 248 seconds]
orivej has joined #picolisp
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #picolisp
orivej has quit [Ping timeout: 248 seconds]
<rick42>
Regenaxer: today, an opebsd dev brian callahan, make a change to a project of his wherein he dropped the dependency on gnu make by writing a simple shell script (called `configure`) which writes out a posix makefile. the aim was portability. now users simply use whatever make program is available on the system. neat approach: https://github.com/ibara/oksh/blob/master/configure
<aw->
hey rick42
<aw->
i have some news, i'll post on the list later, regarding my JSON library
orivej has joined #picolisp
<rick42>
aw-: hey man! ok, looking fwd to it!
<rick42>
gnite from indiana! :)
<aw->
cool! g'nite
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #picolisp
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #picolisp
orivej has quit [Ping timeout: 248 seconds]
orivej has joined #picolisp
aw- has quit [Ping timeout: 260 seconds]
aw- has joined #picolisp
<Regenaxer>
rick42, thanks! Nice, though this does unfortunately not help on other systems. I use Makefile only for other systems, for my own use (eg. building PilBox) I simply use shell scripts with just a handful of lines
rob_w has joined #picolisp
rob_w has quit [Changing host]
rob_w has joined #picolisp
orivej has quit [Ping timeout: 265 seconds]
<Regenaxer>
picoLisp-17.12 available in Debian Sid (now also for arm64)
<aw->
great!
<aw->
i'm still on Stretch for now
<Regenaxer>
ok
orivej has joined #picolisp
<aw->
anyways i'm already on 17.12
<aw->
seems the TinyCore people haven't published 17.12 either
<Regenaxer>
takes time to propagate
<beneroth>
Good morning Regenaxer
<beneroth>
hi aw-
<Regenaxer>
I'm testing now on ppc64 and arm64
<Regenaxer>
hi beneroth
<aw->
hey bene
clacke[m] has quit [*.net *.split]
clacke[m] has joined #picolisp
orivej has quit [Ping timeout: 248 seconds]
<aw->
is there a way to represent scientific numbers in picolisp?
<aw->
ex: 3.7e-5
<aw->
or more specifically, has anyone written any code to work with those?
<Regenaxer>
only as strings
<Regenaxer>
I didn't though
<aw->
because floating point eh... would need to use (native @) perhaps
<aw->
Regenaxer: haha no, that's the only exception HAHAHA
<Regenaxer>
ok :)
<beneroth>
javascript/JSON only having floats (vs. integers) is a real weakness
<aw->
i accept pull requests if someone wants that, but I personally don't care ;)
<beneroth>
I hope you had the fire under control? :D
<aw->
beneroth: ?
<Regenaxer>
Minor optim: Instead of (or (= "," Value) (= ...) you could write (member Value '("," ...)
<Regenaxer>
the or is still needed for lst? etc.
<aw->
oh i'm sure there's many optimizations possible
<aw->
what line?
<beneroth>
aw-, kill git submodule with fire :)
<Regenaxer>
yeah, not critical
<aw->
beneroth: haha oh yeah that was a while back when i switched from git submodules to Makefile
<Regenaxer>
Why is it necessary to throw errors?
<beneroth>
what issues did you encounter/see with git submodules?
<beneroth>
(I currently use git submodules)
<Regenaxer>
you could also 'quit' instead of 'throw' and catch the errors
<aw->
Regenaxer: quit doesn't return NIL
<aw->
Regenaxer: that would break backwards compat with the older lib
<aw->
i don't want to change my existing programs
<aw->
so a failure needs to always return NIL
<Regenaxer>
You can catch quit the same way
<Regenaxer>
What does it return?
<aw->
beneroth: submodules are painful sometimes, like if you edit the code in the submodule and don't commit/push correctly, it breaks for other people
<Regenaxer>
I would expect NIL too
<beneroth>
what does your program return in case of success?
<beneroth>
aw-, hm. yeah true. user error though.
<aw->
beneroth: the list (parsed list)
<Regenaxer>
ah, right, it returns the error. OK
<Regenaxer>
good point
<aw->
beneroth: too much user error with submodules, too easy to screw up and then it's a pain to fix, i got "burned" by them so often.. it's fine if you're the only dev, but really painful with multiple people on the same repo
<beneroth>
two people at the moment
<beneroth>
but yeah
<beneroth>
haven't got burned yet. thanks for sharing your experience :)
<aw->
beneroth: they work really well, but require discipline
<beneroth>
T
<aw->
Regenaxer: thanks
<beneroth>
discipline is the major problem with software dev, I find...
<Regenaxer>
indeed
<beneroth>
the 4 problems of software industry: 1. discipline, 2. naming things, 3. off-by-one errors
<Regenaxer>
4. Not really thinking about one is doing