06:55 <d_bot> <Jektrix> Lmao this comment made me laugh https://www.reddit.com/r/programming/comments/7wbtg/comment/c07lbu9/?utm_source=share&utm_medium=web2x&context=3

06:56 <d_bot> <Jektrix> > Oleg built his house out of Prolog relations

11:39 <hackinghorn> I'm trying to solve some programming problems. Read an int n, and for n times, read some ints, x, y, and do things, is there a functional way to for n times?

11:46 <d_bot> <undu> A recursive function with a parameter that actes as a counter, on every recursive call, add 1 to the parameter

11:47 <hackinghorn> ah thanks, I can do that

11:48 <hackinghorn> let me know alternatives, too

12:01 <d_bot> <orbitz> you can count up, or down

12:01 <d_bot> <orbitz> left or right

12:10 <unmatched-paren> hi! is there an equivalent in ocamllex to the caret (^) in regex, to match a character/sequence only if it's the first in a rule?

12:10 <unmatched-paren> i can't find anything on the internet, so i'm guessing no

12:20 <d_bot> <darrenldl> (seems like a weird requirement

12:24 <d_bot> <Et7f3> It can be handled in the parser step (ie follow \n

12:26 <d_bot> <darrenldl> does ^ in presumably regex demand no preceeding whitespace?

12:30 <unmatched-paren> well, i'm writing a toy pascal compiler, and most pascal compilers have a compiler directive thing similar to c's #preprocessor, except it's specified in comments

12:30 <unmatched-paren> so, for example: {$ifdef some_def}

12:31 <unmatched-paren> or (*$define foo*)

12:31 <unmatched-paren> that $ needs to be at the beginning

12:32 <unmatched-paren> otherwise it's just a regular character

12:32 <unmatched-paren> i tried ^

12:41 <d_bot> <Et7f3> Then try to match ($ or {$

12:41 <unmatched-paren> i considered that, but

12:42 <unmatched-paren> ...actually, you're probably right.

12:46 <unmatched-paren> i was trying to integrate them both in one rule (1) to make the code smaller and (2) because most pascal compilers ignore any text beyond the fields that a control comment accepts, so {$ifdef foo bar} is equivalent to {$ifdef foo}, but i realized that i could just invoke the comment rule once that point is reached

15:11 <d_bot> <darrenldl> interesting(?) find of the day: some time zone offsets are defined at the second granularity apparently

15:15 <d_bot> <VPhantom> Wow.

15:16 <d_bot> <VPhantom> I heard about some being 15 minutes but never finer.

15:54 <d_bot> <darrenldl> i uh, i have no clue if it's to do with my tzdb data collecting code, but i'm just gonna add the changes so the new tests are happy

15:57 <d_bot> <darrenldl> qcheck always trips all the edge cases

15:57 <d_bot> <darrenldl> (and crowbar/afl

16:59 <d_bot> <darrenldl> might be time to bump timedesc to 1.0.0 hmm

17:01 <d_bot> <darrenldl> unmatched-paren: yeah just do it in a pass after parsing etc

17:02 <d_bot> <darrenldl> unless you want to be very precise, accepting a more lenient syntax seems fine