<infinisil>
Not sure why you ping me for that but nice :)
<infinisil>
I just had my compiler design exam a few days ago, in which I had to know about top-down and bottom-up parsing (not sure what the methods are called exactly though)
<__monty__>
Knowledge in, knowledge out? In a matter of days : p
<infinisil>
Heh I don't even think so, it was quiet an interesting course and I'm very interested in programming languages in general
<infinisil>
Just looked it up: the bottom-up kind was an SLR parser. I now know how to do it by hand :P
ldlework has quit [Read error: Connection reset by peer]
<srk>
"First, the combinator library can explicitly expose backtracking primitives to the user of the library, so that programmers can control when backtracking can occur. This does resolve the problem, but a drastic price: there is basically no specification of the accepted language beyond the actual code of the parser implementation."
<srk>
not really "drastic price" IMO :P
<gchristensen>
loads of languages have no spec beyond the implementation!
<srk>
nice thing about parser combinators is that you can write parsers at 3am without much thinking, it's just totally straightforward after a while
<andi->
Isn't 3am peak-productivity? :)
<gchristensen>
by 3am I've already been asleep for 5hrs :')
<andi->
wow
<andi->
I never manage that
<simpson>
I slept a 9-5 in my local time zone. It's nearly 7AM right now.
<jD91mZM2>
samueldr: joepie91: IT'S WORKING! It's scanning the ENTIRE nixpkgs, parsing all files, then converting them back to strings and comparing with the original
<jD91mZM2>
After fixing an issue with interpolation, it's still going after well over a minute of running
<samueldr>
awesome
<infinisil>
:O neat
<jD91mZM2>
All thanks to matklad's help
<samueldr>
while I know some scoff(s|ed) at the way you did it, IDGAF, thank you for doing the thing :D
<gchristensen>
very cool
<jD91mZM2>
He explained how Swift's libsyntax worked and helped me with quite a few design ideas
<jD91mZM2>
What way did I do it wrong?
<jD91mZM2>
(samueldr)
<samueldr>
I thought you rolled down your own parser?
<gchristensen>
the cool thing is we don't have to "redistribute" it
<gchristensen>
so we can do it
<pie_>
gchristensen, now that you mention it :D
<samueldr>
it kinda leaves a sour taste... like PR and legal decided to throw all sense away
<pie_>
b.u.s.i.n.e.s.s. :D
jtojnar has joined #nixos-chat
drakonis_ has quit [Remote host closed the connection]
sir_guy_carleton has joined #nixos-chat
sir_guy_carleton has quit [Quit: WeeChat 2.0]
sir_guy_carleton has joined #nixos-chat
sir_guy_carleton has quit [Client Quit]
sir_guy_carleton has joined #nixos-chat
<aszlig>
pie_: i'm complaining about what? O_o
<pie_>
that bit instead of byte based parsing in haskell isnt great
<aszlig>
pie_: but yeah, erlang bitstrings are quite wonderful for parsing binary blurb, especially if it comes to binary networking protocols
<pie_>
aszlig, do you have any advice on the haskell side?
<aszlig>
pie_: i think the last time i did binary parsing in haskell i used instances of Binary
<pie_>
yeah ive run into Binary.Bits and something else i think
<pie_>
there does seem to be two or three established looking approaches
<aszlig>
but it's not as nice as <<X:2, Y:6>>
<aszlig>
maybe there exists a quasi quoter for something like that now, haven't looked since quite a while
<pie_>
i havent seen anything new
<pie_>
doesnt mean it doesnt exist though
jD91mZM2 has quit [Quit: WeeChat 2.0]
<elvishjerricco>
Hm. I was interested in making a tail recursive bash script by ending with `exec $0`, just to get it to auto-update the code being run when the script changes. I know this is a terrible idea, but I was surprised to find that it grows in space usage over time.
<elvishjerricco>
Very, very slowly.
<elvishjerricco>
Like 2min of just `exec $0` and nothing else to get to 10G used.
drakonis_ has joined #nixos-chat
tertle||eltret has quit [Quit: Connection closed for inactivity]