00:00:00 --- log: started forth/18.01.14 00:10:17 cheater, if you wanna see something close to DS expressed in forth check out the Timbre project: http://clubweb.interbaun.com/~rc/Timbre/index.html 00:29:17 --- quit: Zarutian_PI (Ping timeout: 256 seconds) 01:38:13 --- quit: lijero (Remote host closed the connection) 01:44:27 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 01:50:06 --- part: ircer2 left #forth 02:28:38 --- quit: dddddd (Remote host closed the connection) 03:13:57 --- join: jedb (~jedb@199.66.90.209) joined #forth 03:18:52 --- join: gravicappa (~gravicapp@h178-129-89-229.dyn.bashtel.ru) joined #forth 04:36:19 --- join: ircer2 (~ircer2@185.230.125.164) joined #forth 04:47:26 --- quit: ircer2 (Read error: Connection reset by peer) 05:42:50 --- join: ncv_ (~neceve@2a02:c7d:c5c9:a900:c792:a3e8:397d:b37) joined #forth 05:42:50 --- quit: ncv_ (Changing host) 05:42:50 --- join: ncv_ (~neceve@unaffiliated/neceve) joined #forth 05:50:44 DS *expressed* in forth? really? 05:59:36 well the transformations in a manner similar to DS. remember I said similar. DS is king of an academic "purist" representation. Forthers tend to take what's practical from such things and work around the impractical aspects in their implementations. 06:00:02 cheater, look at the link and tell me what you think. The guy has done some very cool transformations in very little forth code. 06:05:16 yeah i understand 06:05:31 i've been looking through it 06:52:02 --- quit: ThirtyOne32nds (Read error: Connection reset by peer) 07:20:05 --- quit: malyn (Read error: Connection reset by peer) 07:20:22 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 07:24:54 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 07:56:19 Excellent examples of how the most useful forth apps are generally DSLs of their own executed as straight-up forth words. 08:00:03 --- join: Zarutian_PI (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 08:28:42 ryoshu, check out the link I posted earlier for the Timbre project for a good example of a forth app. 08:52:11 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 09:05:20 --- join: ThirtyOne32nds (~rtmanpage@124.sub-174-204-9.myvzw.com) joined #forth 09:21:51 --- join: dys (~dys@tmo-109-190.customers.d1-online.com) joined #forth 09:37:04 --- quit: Zarutian_PI (Read error: Connection reset by peer) 09:37:13 --- join: Zarutian_PI (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 09:47:45 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 10:11:38 --- quit: dys (Remote host closed the connection) 11:23:09 --- quit: gravicappa (Ping timeout: 255 seconds) 12:07:22 cool 12:12:18 --- quit: ncv_ (Ping timeout: 256 seconds) 12:12:52 --- quit: proteusguy (Ping timeout: 260 seconds) 12:13:24 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:1826:4724:e93d:d94e) joined #forth 12:13:24 --- mode: ChanServ set +v proteusguy 12:30:07 --- quit: impomatic (Ping timeout: 264 seconds) 14:00:29 proteusguy looking 14:25:38 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 14:49:16 --- part: DGASAU left #forth 16:31:28 --- join: impomatic (~digital_w@host109-149-154-234.range109-149.btcentralplus.com) joined #forth 17:36:56 --- quit: dddddd (Remote host closed the connection) 17:48:48 proteusguy: i found a benchmark shows gforth-fast even slower than kotlin and java. are there any faster impl ? 18:09:47 yunfan: vfx and iforth 18:13:25 java can be fast 18:13:32 crc how's your retro/pkgsrc? 18:14:46 I'm still slowly working on pkgsrc and freebsd ports packaging of retro 18:15:33 can you commit it to pkgsrc-wip? 18:15:44 as in, have you got access 18:15:49 write bit 18:15:55 no 18:16:44 http://pkgsrc.org/wip/ 18:17:03 crc: will they beat java? 18:17:13 crc: also how they got faster? 18:18:06 ryoshu: thanks 18:18:43 yunfan: no idea vs java. vfx has some timings comparions at http://www.mpeforth.com/software/pc-systems/vfx-forth-common-features/#vfxcode 18:19:20 yunfan: vfx and iforth both have optimizing compilerz. most forth implementations do not. 18:21:59 crc: so they use technology like JIT? to emit native code in runtime? 18:24:27 vfx generates native code directly, no JIT. I'm not sure about iforth as I've not used that. 18:26:03 ok 19:34:06 crc: i checked the benchmarks, it looks like botht vfx and iforth could beaten gforth-fast in 2 or 3 times 19:34:23 that's looks like beaten kotlin in the report i read 19:34:27 happier :D 19:34:50 but dunno, why gff has many 0ms score in some test 19:37:01 --- quit: proteusguy (Remote host closed the connection) 20:52:32 --- join: nighty-- (~nighty@kyotolabs.asahinet.com) joined #forth 21:09:25 --- quit: Gromboli (Quit: Leaving) 22:43:04 --- quit: lijero (Remote host closed the connection) 23:39:43 --- join: mtsd (4d6e3d64@gateway/web/freenode/ip.77.110.61.100) joined #forth 23:59:59 --- log: ended forth/18.01.14