00:00:00 --- log: started forth/19.05.31 00:47:52 WilhelmVonWeiner, agree re: queues and stacks being "sister structures". I have in mind a "mark" word which remembers a position on the stack as the beginning of a queue (in a purpose made register most likely). Then you can use queue-oriented words that will act on those items as a queue starting at MARK and ending at TOS. Naturally you will need to clear the queue to the point of MARK before you resume full stack based 00:47:53 operations. Haven't implemented it yet but I think it meets some use cases I had in mind well. 00:59:56 --- join: dys (~dys@tmo-118-128.customers.d1-online.com) joined #forth 01:36:14 ah, good approach 01:36:38 barely even a compromise 01:42:20 --- join: DKordic (~user@178-222-26-80.dynamic.isp.telekom.rs) joined #forth 01:46:30 wouldn't really even need "queue oriented" words 01:53:41 You could do all kinds of crazy data structures. Tree instead of stacks, oh the humanity 02:04:42 --- quit: ashirase (Ping timeout: 258 seconds) 02:09:00 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 03:22:31 --- quit: proteusguy (Ping timeout: 258 seconds) 03:34:55 --- join: proteusguy (~proteusgu@cm-58-10-155-156.revip7.asianet.co.th) joined #forth 03:34:55 --- mode: ChanServ set +v proteusguy 05:24:15 --- join: rann_ (sid175221@gateway/web/irccloud.com/x-nfiqygeuazsyytdl) joined #forth 05:24:59 --- quit: rprimus (Ping timeout: 245 seconds) 05:25:40 --- quit: crc (Ping timeout: 268 seconds) 05:26:08 --- quit: rann (Ping timeout: 252 seconds) 05:26:14 --- join: crc_ (crc@2a01:7e00::f03c:91ff:fe12:ac) joined #forth 05:26:19 --- quit: KipIngram (Ping timeout: 252 seconds) 05:26:25 --- nick: rann_ -> rann 05:26:48 --- nick: crc_ -> crc 05:27:03 --- mode: ChanServ set +v crc 05:28:45 --- join: KipIngram (~kipingram@185.149.90.58) joined #forth 05:29:10 --- nick: KipIngram -> Guest5481 05:31:51 --- join: rprimus (~micro@unaffiliated/micro) joined #forth 07:33:39 --- quit: lonjil (Ping timeout: 258 seconds) 07:35:02 --- join: lonjil (~quassel@2a02:418:6050:ed15:ed15:ed15:e741:32d6) joined #forth 07:53:36 --- quit: tabemann (Ping timeout: 248 seconds) 07:58:58 --- nick: Guest5481 -> KipIngram 07:59:27 --- nick: KipIngram -> Guest28349 08:00:08 --- nick: Guest28349 -> KipIngram 08:00:17 --- mode: ChanServ set +v KipIngram 08:10:13 --- quit: deesix (Ping timeout: 246 seconds) 08:10:49 --- quit: dddddd (Ping timeout: 245 seconds) 08:21:11 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 08:22:52 --- join: deesix (~dddddd@unaffiliated/dddddd) joined #forth 08:43:40 * Zarutian ran into bit of a problem with that dungeon maze generation challange. 08:44:43 it isnt that I do not know how to do something but it is basically choice anxiety for the maze generation par, which of http://www.astrolog.org/labyrnth/algrithm.htm#perfect should I choose! They all sound nifty to implement. 08:45:20 --- quit: dys (Ping timeout: 258 seconds) 09:42:49 --- quit: reepca (Ping timeout: 268 seconds) 10:13:07 --- quit: xek_ (Ping timeout: 258 seconds) 10:26:02 i like kruskal's algorithm 10:32:16 --- quit: `presiden (Read error: Connection reset by peer) 10:32:22 --- join: `preside1 (~presiden@unaffiliated/matematikaadit) joined #forth 11:44:00 --- join: cnidario (~aaa@92.57.58.87) joined #forth 11:49:30 --- quit: dave0 (Quit: dave's not here) 12:15:14 --- quit: gravicappa (Ping timeout: 272 seconds) 12:19:22 --- nick: `preside1 -> `presiden 13:12:12 --- join: xek_ (~xek@apn-37-248-138-83.dynamic.gprs.plus.pl) joined #forth 13:36:51 --- join: bluekelp (~pp@bluekelp.com) joined #forth 13:44:16 --- quit: cnidario (Remote host closed the connection) 14:18:13 --- quit: pierpal (Ping timeout: 248 seconds) 14:49:09 --- quit: xek_ (Ping timeout: 248 seconds) 14:57:56 --- quit: lonjil (Ping timeout: 257 seconds) 15:02:54 --- join: lonjil (~quassel@2a02:418:6050:ed15:ed15:ed15:e741:32d6) joined #forth 15:48:14 --- quit: ghostyy (Read error: Connection reset by peer) 16:11:44 --- quit: john_cephalopoda (Ping timeout: 248 seconds) 16:25:22 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 17:27:28 --- join: tabemann (~tabemann@h193.235.138.40.static.ip.windstream.net) joined #forth 18:20:52 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 18:21:31 hi 18:25:11 <`presiden> morning 18:26:35 --- quit: dddddd (Read error: Connection reset by peer) 18:27:20 hi `presiden 18:45:01 --- quit: dave0 (Quit: dave's not here) 19:05:02 --- join: reepca (~user@208.89.170.37) joined #forth 19:17:35 hey guys 19:22:48 3HI TABEMANN 19:33:30 --- quit: tabemann (Ping timeout: 272 seconds) 19:46:17 --- join: tabemann (~tabemann@h193.235.138.40.static.ip.windstream.net) joined #forth 19:47:03 well, at the moment, it seems like the allocator works 20:03:16 --- quit: tabemann (Ping timeout: 272 seconds) 20:26:45 --- join: tabemann (~tabemann@2600:1700:7990:24e0:b944:a349:56b9:12fb) joined #forth 20:32:38 --- join: gravicappa (~gravicapp@h109-187-8-54.dyn.bashtel.ru) joined #forth 20:55:07 --- quit: dave9 (Quit: dave's not here) 20:55:43 --- join: dave9 (~dave@069.d.003.ncl.iprimus.net.au) joined #forth 21:31:09 --- quit: ullbeking (Ping timeout: 252 seconds) 21:34:05 --- quit: arrdem__ (Ping timeout: 252 seconds) 21:41:42 --- join: arrdem__ (sid333803@gateway/web/irccloud.com/x-rpijbakidlfthkin) joined #forth 21:52:01 --- join: ullbeking (sid5364@gateway/web/irccloud.com/x-jqxvmqonynqczvpj) joined #forth 22:37:32 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 22:38:33 re 22:49:53 wb 23:07:12 <`presiden> ty 23:59:59 --- log: ended forth/19.05.31