00:00:00 --- log: started forth/17.12.21 00:08:30 --- quit: dys (Ping timeout: 252 seconds) 01:03:25 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 01:29:54 Zarutian_PI: why are types abstract and type tags not abstract? i don't understand the difference 01:35:59 --- quit: Uniju (Quit: Feeling down? You may already be a charge target.) 02:07:20 cheater, strong types that, upon compilation, guarantee the code is correct is a pretty strong guarantee. It also helps address a core problem with forth in that it does not scale well as a language in terms of team size. This is because the system communicates no guarantees about the code and its data structure's behaviour. Types do this so developers can understand each other's code much easier. Ever seen a forth project with more than 2 or 3 02:07:20 devs that was successful and stuck to forth's principles? I haven't. That's a big part of the reason why, IMHO. 02:07:40 cheater, but I agree it's not enough by itself. But it is a very strong beginning. 02:21:13 --- quit: jedb_ (Ping timeout: 260 seconds) 02:38:31 --- join: jedb_ (~jedb@123.100.37.244) joined #forth 02:46:20 --- quit: proteusguy (Remote host closed the connection) 02:47:24 --- quit: jedb_ (Ping timeout: 268 seconds) 02:47:45 --- join: jedb_ (jedb@gateway/vpn/mullvad/x-mmmkvkozmjjzfmms) joined #forth 03:23:30 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 03:28:53 proteus-guy: i agree with your motivation 03:38:42 --- quit: nighty-- (Quit: Disappears in a puff of smoke) 05:36:13 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:990e:53cc:937e:2a70) joined #forth 05:36:13 --- mode: ChanServ set +v proteusguy 06:11:10 cheater: with tags the list of kinds of values is finite while with types it is unbounded. 06:24:03 Zarutian_PI: why? i assume you're going by some specific definition of types and tags. could you bring them up? 06:24:20 i'd like to read that please so that i can understand it better 06:51:29 You could look at how object store of SmallTalk80/Squeak is implemented or how various Schemes do values. 07:32:36 --- join: ncv (~neceve@2a02:c7d:c5c9:a900:c792:a3e8:397d:b37) joined #forth 07:32:36 --- quit: ncv (Changing host) 07:32:36 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 07:48:56 traditional forth's indefinite loop words are all backwards 07:49:08 well, not "all" 07:49:17 specifically begin and while are wrong, imo 07:49:25 and repeat 07:50:00 I'm thinking of rewriting it like this: repeat begin while 07:50:12 but you can replace while with until in that case to get a free negation 07:51:04 and if you want an always-execute-at-least-once loop, it would be "repeat' until" or "repeat' while", but I need better words for repeat and repeat' 07:57:51 arg, I know I've babbled in here about loops before. my problem is that I can't settle on how to name words, so I left it for a while and am finally revisiting it. I think I finally know what collection of words I want and how they'd work, but I'm still hung up on naming 07:59:19 --- quit: gravicappa (Ping timeout: 240 seconds) 08:45:59 --- join: gravicappa (~gravicapp@ppp83-237-165-136.pppoe.mtu-net.ru) joined #forth 09:41:36 --- quit: gravicappa (Ping timeout: 252 seconds) 09:57:38 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 10:02:54 --- part: DGASAU left #forth 10:14:36 --- quit: Zarutian_PI (Read error: Connection reset by peer) 10:14:51 --- join: Zarutian_PI (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 10:31:13 --- quit: nonlinear (Ping timeout: 260 seconds) 10:38:09 --- quit: dys (Ping timeout: 265 seconds) 10:55:50 --- join: dys (~dys@tmo-122-164.customers.d1-online.com) joined #forth 11:44:34 --- join: nonlinear (~nonlinear@unaffiliated/discrttm) joined #forth 13:23:27 --- quit: dys (Ping timeout: 240 seconds) 14:05:46 --- quit: ncv (Ping timeout: 272 seconds) 14:53:00 --- quit: Zarutian_PI (Read error: Connection reset by peer) 14:53:12 --- join: Zarutian_PI (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 16:07:07 --- join: [1]MrMobius (~MrMobius@h8.71.186.173.dynamic.ip.windstream.net) joined #forth 16:07:22 --- quit: MrMobius (Ping timeout: 272 seconds) 16:07:22 --- nick: [1]MrMobius -> MrMobius 16:25:29 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 17:10:04 --- join: nighty-- (~nighty@kyotolabs.asahinet.com) joined #forth 17:18:45 --- quit: nighty- (Remote host closed the connection) 17:22:21 Zarutian_PI: that's a bit too involved for me. do you have a self-contained definition? 17:56:39 --- quit: dddddd (Remote host closed the connection) 18:12:18 --- join: rtmanpages (~rtmanpage@114.sub-174-204-19.myvzw.com) joined #forth 18:14:46 --- quit: ThirtyOne32nds (Ping timeout: 248 seconds) 18:19:48 --- nick: rtmanpages -> ThirtyOne32nds 20:03:05 --- quit: Gromboli (Quit: Leaving) 23:59:59 --- log: ended forth/17.12.21