00:00:00 --- log: started forth/14.07.22 01:56:14 --- nick: ttmrichter -> Textmod 01:56:32 --- nick: Textmod -> ttmrichter 02:29:38 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 02:55:26 --- quit: joneshf-laptop (*.net *.split) 02:55:27 --- quit: backer (*.net *.split) 02:55:27 --- quit: c00kiemon5ter (*.net *.split) 02:55:34 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 02:55:40 --- join: backer (~backer@user-1087i73.cable.mindspring.com) joined #forth 02:56:46 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 03:59:54 --- quit: karswell (Ping timeout: 260 seconds) 04:07:45 --- join: lewis1711 (~lewis@122-59-194-155.jetstream.xtra.co.nz) joined #forth 04:21:16 --- join: saml_ (~saml@pool-71-190-5-241.nycmny.east.verizon.net) joined #forth 04:44:42 --- quit: lewis1711 (Ping timeout: 260 seconds) 05:24:54 --- join: elaforest (~elaforest@unaffiliated/elaforest) joined #forth 05:35:37 --- join: true-grue (~grue@128-69-60-83.broadband.corbina.ru) joined #forth 05:57:37 --- quit: saml_ (Ping timeout: 264 seconds) 06:01:19 --- join: xyh (~user@222.58.65.92) joined #forth 06:14:20 --- part: xyh left #forth 06:51:04 --- join: xyh (~user@222.58.65.92) joined #forth 07:22:49 --- part: xyh left #forth 08:30:29 --- join: xyh (~user@222.58.65.92) joined #forth 09:42:20 What's the state of Forth specification tools? If I wanted to implement Forth, is there an official way to tell if I've implemented it correctly? 09:43:49 no IMO 09:55:03 --- quit: c00kiemon5ter (Ping timeout: 260 seconds) 09:55:10 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 09:58:04 krainboltgreene: by ``Forth-specification-tools'' you mean reusable library ?? 10:00:52 No, I mean documentation, binaries, or anything else that might be useful in describing the Forth specification or checking if a Forth implementation does the right thing. 10:20:51 there are standards, but I think forth is not a very well standardized language, there are many implementation technics and many forth dialects. 10:37:26 Seems like a shame, but I can understand why. 10:49:54 Just read a quote that personifies it: 10:49:55 "The good news is you can do anything with Forth, the bad news is you will probably have to do it yourself." -- David Sands 10:56:44 it is cool to me, many implementation technics and dialects means forth is very interesting and very worth to implement. and I love forth, you will never be alone if you implement your own forth 10:58:41 That's a pretty compelling point, I'll agree. But it seems to be that in practice it means the sacrifice of shared tooling. 10:58:55 For example, you'll never see RubyGems or NPM for Forth. 11:03:00 maybe you will see a good package manager for a great forth dialect in the future, who knows :) 11:40:41 the concept of ``exokernel'' sounds like a refactoring to me ! --> http://wiki.osdev.org/Exokernel 11:41:00 with some steps forward ``exokernel'' will be ``no-kernel,only-forth'' 12:06:19 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 12:28:16 --- quit: xyh (Remote host closed the connection) 12:28:41 --- join: xyh (~user@222.58.65.92) joined #forth 12:34:39 --- quit: Zarutian (Ping timeout: 260 seconds) 12:49:13 krainboltgreene, xyh: gforth aims to be more precise standard. This is best package index I have heard of: http://soton.mpeforth.com/flag/index.html 12:49:26 xyh: I agree. 12:51:23 dkordic: Yeah, that seems like a pretty good effort. 12:52:52 --- quit: xyh (Remote host closed the connection) 13:35:13 --- quit: elaforest (Ping timeout: 240 seconds) 13:42:43 --- quit: true-grue (Read error: Connection reset by peer) 14:40:02 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 14:44:01 --- join: kumul (~mool@adsl-72-50-84-29.prtc.net) joined #forth 15:21:22 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 15:24:05 --- quit: fayisha (Remote host closed the connection) 15:37:25 --- quit: kumul (Ping timeout: 240 seconds) 15:39:13 --- join: kumul (~mool@adsl-72-50-84-29.prtc.net) joined #forth 15:41:42 --- quit: Zarutian (Ping timeout: 245 seconds) 15:42:34 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 15:51:46 --- join: karswell (~user@0.200.90.146.dyn.plus.net) joined #forth 16:06:57 --- join: MrMobius (~Joey@178.sub-70-198-193.myvzw.com) joined #forth 16:45:38 --- quit: MrMobius (Ping timeout: 264 seconds) 16:55:56 --- quit: Zarutian (Ping timeout: 240 seconds) 16:59:14 --- join: ErhardtTheWhite (~quassel@93-43-168-8.ip92.fastwebnet.it) joined #forth 17:00:25 --- quit: ErhardtMundt (Ping timeout: 240 seconds) 17:00:55 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 17:01:33 --- quit: kumul (Ping timeout: 255 seconds) 17:20:57 --- quit: Zarutian (Ping timeout: 245 seconds) 17:26:44 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 17:46:29 --- join: MrMobius (~Joey@178.sub-70-198-193.myvzw.com) joined #forth 18:12:07 --- quit: I440r (Ping timeout: 245 seconds) 18:22:46 --- quit: MrMobius (Read error: Connection reset by peer) 18:34:29 --- join: MrMobius (~Joey@178.sub-70-198-193.myvzw.com) joined #forth 18:37:18 --- quit: Zarutian (Quit: Zarutian) 18:44:14 --- join: kumul (~mool@adsl-72-50-87-93.prtc.net) joined #forth 18:44:51 --- quit: kumul (Client Quit) 19:17:34 --- join: saml_ (~saml@pool-71-190-5-241.nycmny.east.verizon.net) joined #forth 20:24:14 --- join: kumul (~mool@adsl-72-50-84-93.prtc.net) joined #forth 20:34:59 --- quit: saml_ (Ping timeout: 250 seconds) 20:48:58 --- quit: MrMobius (Quit: HydraIRC -> http://www.hydrairc.com <- Would you like to know more?) 21:39:34 --- join: MrMobius (~Joey@c-71-206-218-187.hsd1.wv.comcast.net) joined #forth 23:05:28 --- quit: MrMobius (Read error: Connection reset by peer) 23:33:55 --- quit: kumul (Quit: Leaving) 23:59:59 --- log: ended forth/14.07.22