2024/09/20

Newest at the top

2024-09-20 21:33:48 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds)
2024-09-20 21:29:01 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 21:28:28 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 252 seconds)
2024-09-20 21:27:35 +0200ChanServ+v haskellbridge
2024-09-20 21:27:35 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com)
2024-09-20 21:27:18 +0200Pixi(~Pixi@user/pixi)
2024-09-20 21:26:52 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection)
2024-09-20 21:20:14 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 255 seconds)
2024-09-20 21:19:50 +0200Smiles(uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-09-20 21:18:45 +0200athan(~athan@syn-098-153-145-140.biz.spectrum.com) (Ping timeout: 248 seconds)
2024-09-20 21:15:19 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 21:13:54 +0200mreh(~matthew@host86-146-25-125.range86-146.btcentralplus.com)
2024-09-20 21:05:14 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 21:04:21 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-09-20 21:00:40 +0200caconym(~caconym@user/caconym)
2024-09-20 21:00:03 +0200caconym(~caconym@user/caconym) (Quit: bye)
2024-09-20 20:59:31 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 20:48:43 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds)
2024-09-20 20:46:54 +0200athan(~athan@syn-098-153-145-140.biz.spectrum.com)
2024-09-20 20:44:13 +0200misterfish(~misterfis@84.53.85.146)
2024-09-20 20:43:44 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 20:37:45 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 276 seconds)
2024-09-20 20:33:14 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-09-20 20:32:37 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 20:27:58 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 20:23:15 +0200 <lxsameer> mauke: yeah, that makes it much easier
2024-09-20 20:23:00 +0200 <lxsameer> mauke: hmmm cool, thank you. I'll give it a shot
2024-09-20 20:22:57 +0200 <mauke> if the symbol name cleanly converts to a number, it is a number
2024-09-20 20:22:37 +0200 <mauke> yeah, basically
2024-09-20 20:21:55 +0200 <lxsameer> mauke: are you suggesting to parse them as symbol and the run another number parser on the symbol ?
2024-09-20 20:21:16 +0200 <lxsameer> geekosaur: i'm in charge of the lang, so I can change the grammar if I want to
2024-09-20 20:21:15 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) (Ping timeout: 265 seconds)
2024-09-20 20:20:57 +0200 <lxsameer> mauke: technically yes.
2024-09-20 20:20:41 +0200 <mauke> aren't numbers just a type of symbol, syntactically?
2024-09-20 20:20:36 +0200 <geekosaur> because C supports things like 1L, 1ULL, etc.
2024-09-20 20:20:22 +0200 <geekosaur> yes, what language you're parsing matters too. gcc parses character suffixes after numbers and reports errors if the suffix(es) aren't valid ("error: invalid suffix "a" on integer constant")
2024-09-20 20:19:26 +0200 <lxsameer> mauke: yupe
2024-09-20 20:19:19 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 264 seconds)
2024-09-20 20:18:35 +0200Versatile(~Versatile@2.219.56.221)
2024-09-20 20:18:34 +0200 <mauke> lxsameer: are you parsing a lisp?
2024-09-20 20:17:46 +0200 <lambdabot> 42
2024-09-20 20:17:45 +0200 <mauke> > let a = -1 in (+) 43a
2024-09-20 20:17:26 +0200ash3en(~Thunderbi@2a01:c23:8c85:a600:95cb:522:a5ea:bb0d)
2024-09-20 20:17:07 +0200 <geekosaur> that's usually handled by the grammar: if 'a' isn't valid following the number then you get a parse error
2024-09-20 20:16:48 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 246 seconds)
2024-09-20 20:16:36 +0200 <lxsameer> geekosaur: hmm it will, but it uses 'a' as a terminator an returns -43 as a number
2024-09-20 20:15:44 +0200 <geekosaur> most parsers including combinator-based ones use a "maximal munch" rule, so if you parse as a number it should fail at the 'a'
2024-09-20 20:14:19 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 20:14:11 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2024-09-20 20:14:02 +0200 <lxsameer> hey folks, how do you parse a string like '-43a' with megaparse or any parser combinator? -43a is a valid "symbol name" but not a valid number. If parse symbols first that's fine but then I will accidentally parse valid numbers as symbol too