Newest at the top
| 2026-03-06 22:40:00 +0100 | Googulator | (~Googulato@2a01-036d-0106-0119-01e8-0aed-2fac-7c8a.pool6.digikabel.hu) |
| 2026-03-06 22:39:43 +0100 | Googulator | (~Googulato@2a01-036d-0106-0119-01e8-0aed-2fac-7c8a.pool6.digikabel.hu) (Quit: Client closed) |
| 2026-03-06 22:34:36 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-03-06 22:29:48 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-03-06 22:28:36 +0100 | <[exa]> | lol |
| 2026-03-06 22:28:07 +0100 | <EvanR> | what an unfortuante elision in the url |
| 2026-03-06 22:27:42 +0100 | <[exa]> | that post is priceless^^ |
| 2026-03-06 22:27:22 +0100 | <int-e> | EvanR: because whether something is a type depends on template instantiations and those are Turing complete (not accounting for compiler-imposed limits on said instantiations). sketch: https://blog.reverberate.org/2013/08/parsing-c-is-literally-undecidable.html |
| 2026-03-06 22:27:17 +0100 | <[exa]> | EvanR: you can pull some context through the semantics right? (like they do with the stateful computations) |
| 2026-03-06 22:26:14 +0100 | spew | (~spew@user/spew) (Quit: nyaa~) |
| 2026-03-06 22:25:52 +0100 | <EvanR> | C++ parsing is undecidable? |
| 2026-03-06 22:24:56 +0100 | <int-e> | At least it's decidable? (C++ parsing famously isn't) |
| 2026-03-06 22:24:33 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2026-03-06 22:23:42 +0100 | <int-e> | EvanR: I had to google but there's something very simple: a * b; can be an expression whose value is ingored or a declarion of a variable of type (a *), depending on what a is. |
| 2026-03-06 22:21:19 +0100 | spew | (~spew@user/spew) spew |
| 2026-03-06 22:19:48 +0100 | <int-e> | EvanR: hah, I parsed that as a question. |
| 2026-03-06 22:19:21 +0100 | <EvanR> | [exa] ^ |
| 2026-03-06 22:19:00 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-03-06 22:18:07 +0100 | <int-e> | aren't |
| 2026-03-06 22:17:57 +0100 | <int-e> | EvanR: Very standard restrictions like "identifier has to be declared before use" isn't context-free. |
| 2026-03-06 22:17:54 +0100 | <EvanR> | I vague recall something weird with the parsing of expressions containing * in C |
| 2026-03-06 22:17:05 +0100 | <int-e> | EvanR: pretty much all of them |
| 2026-03-06 22:15:28 +0100 | <EvanR> | any programming language whose syntax isn't context free? |
| 2026-03-06 22:15:23 +0100 | target_i | (~target_i@user/target-i/x-6023099) (Quit: leaving) |
| 2026-03-06 22:14:02 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-03-06 22:13:59 +0100 | <[exa]> | EvanR: kinda wondering what would be a non-denotational thing to get there |
| 2026-03-06 22:13:19 +0100 | Googulator | (~Googulato@2a01-036d-0106-0119-01e8-0aed-2fac-7c8a.pool6.digikabel.hu) |
| 2026-03-06 22:13:05 +0100 | Googulator | (~Googulato@2a01-036d-0106-0119-01e8-0aed-2fac-7c8a.pool6.digikabel.hu) (Quit: Client closed) |
| 2026-03-06 22:10:35 +0100 | tessier_ | (~tessier@ec2-184-72-149-67.compute-1.amazonaws.com) (Ping timeout: 252 seconds) |
| 2026-03-06 22:03:05 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-03-06 21:58:39 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-03-06 21:58:30 +0100 | humasect_ | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 245 seconds) |
| 2026-03-06 21:57:39 +0100 | tromp | (~textual@89-99-43-152.cable.dynamic.v4.ziggo.nl) |
| 2026-03-06 21:56:43 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 264 seconds) |
| 2026-03-06 21:54:10 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 248 seconds) |
| 2026-03-06 21:53:15 +0100 | humasect_ | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2026-03-06 21:48:19 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-03-06 21:46:10 +0100 | rainbyte | (~rainbyte@181.47.219.106) rainbyte |
| 2026-03-06 21:44:35 +0100 | rainbyte_ | (~rainbyte@181.47.219.106) (Read error: Connection reset by peer) |
| 2026-03-06 21:42:54 +0100 | tromp | (~textual@2001:1c00:3487:1b00:28bd:27be:ef6d:1cb5) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2026-03-06 21:42:51 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-03-06 21:41:10 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Quit: CiaoSen) |
| 2026-03-06 21:40:51 +0100 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2026-03-06 21:40:09 +0100 | madresch | (~Thunderbi@user/madresch) madresch |
| 2026-03-06 21:39:24 +0100 | madresch | (~Thunderbi@user/madresch) (Ping timeout: 264 seconds) |
| 2026-03-06 21:37:43 +0100 | pavonia | (~user@user/siracusa) siracusa |
| 2026-03-06 21:36:31 +0100 | <EvanR> | is this basically mirroring denotational semantics, and so restricts the kind things you can get out of these parsers, they have to be denotational |
| 2026-03-06 21:35:59 +0100 | tzh | (~tzh@76.115.131.146) tzh |
| 2026-03-06 21:35:46 +0100 | <EvanR> | recursive descent parsers and parser combinators and even yacc have this notion of "semantic value" of a subparser. The parser not only consumes and accepts some input but yields some value which is intended to be what the input represented (sometimes on a good day, what it was before being serialized) |
| 2026-03-06 21:34:36 +0100 | rainbyte | (~rainbyte@181.47.219.10) (Ping timeout: 264 seconds) |