00:27:30 -!- arseniiv has quit (Ping timeout: 252 seconds).
01:58:26 -!- FreeFull has quit.
01:58:37 -!- Bowserinator_ has changed nick to Bowserinator.
03:36:53 -!- imode has joined.
06:04:33 <zzo38> Is the Ghostscript interpreter API reentrant?
07:41:08 -!- imode has quit (Ping timeout: 245 seconds).
08:27:43 -!- Sgeo__ has joined.
08:31:29 -!- Sgeo_ has quit (Ping timeout: 268 seconds).
08:34:48 <int-e> 'Unless Ghostscript has been compiled with the GS_THREADSAFE define, only one instance at a time is supported.' -- So it depends.
08:36:08 <int-e> Actually... https://ghostscript.com/doc/current/API.htm#new_instance suggests that the answer is "no, but we're working on it" for practical purposes,
08:37:43 <zzo38> OK, but is a single instance reentrant? (For example, can the I/O implementations execute PostScript code?) (I am making it so that it doesn't, and if it does need to, the PostScript code that calls it uses "(%stdin) run".)
08:38:24 <int-e> I don't know. I expect not.
08:41:43 <zzo38> I also expect not, which is acceptable even if it is capable.
09:22:35 <esowiki> [[1+]] https://esolangs.org/w/index.php?diff=68009&oldid=66679 * TwilightSparkle * (+15) /* External resources */
09:49:40 -!- b_jonas has quit (Remote host closed the connection).
10:36:52 -!- Lord_of_Life has quit (Ping timeout: 248 seconds).
10:38:12 -!- Lord_of_Life has joined.
11:03:08 <shachaf> My uint64_t->uint64_t B-tree map is faster than Rust's BTreeMap<u64, u64> and Google's absl::btree_map<uint64_t, uint64_t>
11:04:04 <Taneb> Does it provide the same or an equivalent API?
11:04:28 <shachaf> It proved sets, gets, deletes, and iterators that can be used for range queries.
11:05:51 <shachaf> For the most part it's a pretty naive implementation, just the first thing I wrote down that worked.
11:05:58 <shachaf> It does linear search through nodes and so on.
12:19:59 -!- arseniiv has joined.
12:25:17 <esowiki> [[Intcode]] M https://esolangs.org/w/index.php?diff=68010&oldid=68006 * Int-e * (+3) /* Program Structure */ fix&tweak grammar
13:23:16 -!- ddmm_ has quit (Ping timeout: 248 seconds).
13:23:24 -!- tswett[m] has quit (Ping timeout: 246 seconds).
13:23:24 -!- wmww has quit (Ping timeout: 246 seconds).
13:42:57 -!- kritixilithos has joined.
13:58:49 <esowiki> [[1+]] M https://esolangs.org/w/index.php?diff=68011&oldid=68009 * A * (+2) /* External resources */ Internal link
14:20:56 -!- Hooloovo0 has quit (Quit: Temporarily refracted into a free-standing prism.).
14:33:17 -!- xkapastel has joined.
14:53:59 -!- ddmm_ has joined.
15:43:22 -!- MDead has joined.
15:46:24 -!- MDude has quit (Ping timeout: 248 seconds).
15:46:27 -!- ddmm_ has quit (Remote host closed the connection).
15:46:27 -!- MDead has changed nick to MDude.
15:58:32 -!- ddmm_ has joined.
15:58:59 -!- MDude has quit (Ping timeout: 258 seconds).
16:13:14 -!- Sgeo__ has quit (Read error: Connection reset by peer).
16:13:38 -!- Sgeo__ has joined.
17:09:58 <esowiki> [[Referencement]] N https://esolangs.org/w/index.php?oldid=68012 * Hakerh400 * (+18328) + [[Referencement]]
17:10:48 <esowiki> [[Language list]] https://esolangs.org/w/index.php?diff=68013&oldid=67948 * Hakerh400 * (+20) + [[Referencement]]
17:11:15 <esowiki> [[User:Hakerh400]] https://esolangs.org/w/index.php?diff=68014&oldid=67007 * Hakerh400 * (+20) + [[Referencement]]
17:36:23 -!- sleepnap has quit (Ping timeout: 250 seconds).
17:37:32 -!- LBPHacker has quit (Quit: Entering cryogenic sleep in three, two, on--).
17:39:37 -!- LBPHacker has joined.
18:09:29 -!- wmww has joined.
18:09:29 -!- tswett[m] has joined.
18:24:53 -!- LKoen has joined.
18:34:14 -!- FreeFull has joined.
19:02:57 -!- kritixilithos has quit (Quit: quit).
19:28:41 <esowiki> [[Stackish]] https://esolangs.org/w/index.php?diff=68015&oldid=50348 * CMinusMinus * (+12) /* External resources */
19:30:09 <esowiki> [[TP]] https://esolangs.org/w/index.php?diff=68016&oldid=50344 * CMinusMinus * (+12) /* External resources */
19:33:25 <esowiki> [[Referencement]] M https://esolangs.org/w/index.php?diff=68017&oldid=68012 * Hakerh400 * (+13)
19:46:17 -!- Melvar has quit (Quit: WeeChat 2.4).
19:55:50 -!- Melvar has joined.
20:17:03 -!- LKoen has quit (Remote host closed the connection).
20:19:31 -!- kspalaiologos has joined.
20:19:55 <kspalaiologos> If someone's interested in helping me with the chess engine I said here about the other day
20:31:45 -!- shig_ has quit (Ping timeout: 268 seconds).
20:32:06 -!- shig has joined.
20:47:18 -!- b_jonas has joined.
21:04:47 <zzo38> O, it is the variant without bishops.
21:22:27 -!- kspalaiologos has quit (Quit: Leaving).
21:23:01 -!- xkapastel has quit (Quit: Connection closed for inactivity).
21:55:16 -!- Sgeo__ has quit (Read error: Connection reset by peer).
21:55:44 -!- Sgeo__ has joined.
22:15:36 -!- Lord_of_Life has quit (Read error: Connection reset by peer).
22:17:25 -!- Lord_of_Life has joined.
22:36:55 -!- Lord_of_Life_ has joined.
22:39:38 -!- Lord_of_Life has quit (Ping timeout: 240 seconds).
22:39:50 -!- Lord_of_Life_ has changed nick to Lord_of_Life.
22:52:05 -!- Hooloovo0 has joined.
22:53:08 <int-e> fizzie: your guess for day 16 is working out
23:11:10 <imode-ruby> I've been thinking a lot about context recently, and why people shy away from things like Forth and my language Mode. I'm trying to understand where the middleground is between positional and random access for data you pass around.
23:12:05 <imode-ruby> focusing on the context of an operation is important. I find myself looking around for context whenever I'm presented with some new code.
23:12:40 <imode-ruby> forth and similar languages have an implicit context: you don't have neat points in time where you can save something that came from somewhere, only to recall it again.
23:13:05 <imode-ruby> you instead have to rely on "juggling": placing elements in an active area and then performing operations on them.
23:13:25 <imode-ruby> forth is like baking a cake with only two hands instead of the support of a countertop.
23:14:16 <imode-ruby> you juggle things around until they're in the right position for one step, then you juggle things around for the next step, and so on. likewise for Mode, but you _really feel it_ because there's no load and store ops.
23:17:16 <imode-ruby> figuring out how to do things like building and using objects is difficult, for example, because of the way the juggling works: in Mode, you need the ID of the process at the head of the queue, and then the thing you want to send to it up next. this results in you enqueueing a value, swapping it, duplicating it, saving it for later, doing the send, then recalling it.
23:18:39 <imode-ruby> but with the right macros... this happens: https://hatebin.com/qhbjgbsysn
23:20:43 <imode-ruby> I have a theory that with the right series of primitives, there will be a point where you stop seeing the queue.
23:25:15 -!- LKoen has joined.
23:49:11 -!- LKoen has quit (Quit: “It’s only logical. First you learn to talk, then you learn to think. Too bad it’s not the other way round.”).