00:00:00 --- log: started forth/17.07.08 00:06:20 --- quit: ACE_Recliner (Remote host closed the connection) 01:37:10 --- quit: Keshl (Ping timeout: 248 seconds) 01:41:23 --- join: LeCamarade (~revence@139.59.111.106) joined #forth 01:44:41 --- join: Keshl (~Purple@24.115.185.149.res-cmts.gld.ptd.net) joined #forth 02:39:40 --- join: gravicappa (~gravicapp@h62-133-162-197.dyn.bashtel.ru) joined #forth 02:46:24 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 03:09:54 --- join: GeDaMo (~GeDaMo@212.225.125.110) joined #forth 03:13:26 --- quit: dys (Ping timeout: 240 seconds) 03:35:46 --- join: true-grue (~true-grue@176.14.219.178) joined #forth 04:55:39 --- quit: DGASAU (Ping timeout: 260 seconds) 07:17:11 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 08:23:35 zy]x[yz: I just use push and pop instead of >r and r>. 08:32:57 --- join: mark4 (~mark4@99.30.241.51) joined #forth 09:04:11 I saw some chuck code that used push and pop and have considered it, but haven't made the switch yet 10:07:21 push and pop meaning >r and r> ? 10:07:46 CM once said of ans forth that the ans forth standard does not describe the forth language but a language of the same name 10:07:58 i say the same thing about CMs forths to a point 10:11:41 --- quit: ncv (Remote host closed the connection) 10:21:23 --- quit: karswell (Remote host closed the connection) 10:22:52 --- join: karswell (~user@186.91.199.146.dyn.plus.net) joined #forth 10:49:54 --- join: dys (~dys@ip-109-44-2-11.web.vodafone.de) joined #forth 11:23:05 --- join: proteusguy (~proteus-g@107.77.244.103) joined #forth 11:23:05 --- mode: ChanServ set +v proteusguy 12:14:48 Mark4: yes 12:16:49 --- quit: gravicappa (Ping timeout: 240 seconds) 12:17:36 :) 12:31:49 --- quit: proteusguy (Ping timeout: 260 seconds) 13:20:27 --- join: smokeink (~smoke@171.36.255.9) joined #forth 13:20:34 --- quit: smokeink (Client Quit) 13:30:48 --- quit: dys (Ping timeout: 255 seconds) 13:40:17 --- join: dys (~dys@ip-109-44-1-217.web.vodafone.de) joined #forth 13:57:07 --- join: MickyW (~MickyW@p4FCFEFEF.dip0.t-ipconnect.de) joined #forth 14:10:26 My forth is diverged 14:10:44 Enough from rom traditional for this as to be very incompatible 14:41:19 my forth is designed to have a 83 std feel in 32 bits :P 14:42:30 i forget who it was but someone ws writing an article and wrote "when you have seen one forth you have seen them all" and his daughter said "no daddy, when you have seen one forth you have seen one forth" 14:42:32 BOTH are correct 14:42:56 I think it was Wil Baden 14:43:05 thats possible lol 14:43:27 http://www.wilbaden.com/neil_bawd/wnuvsn1f.html 14:43:56 yup 14:44:01 you stand correctly :) 14:45:53 this is why one should read all forths one can get ones hands on to see the flora of ideas and possibly copy some words over to ones own forth. 14:48:19 or simply understand forth to a great enough level that you just invent what you need when you need it rather than pulling in "cool things" from other places just in case its useful :P 14:48:47 --- quit: GeDaMo (Remote host closed the connection) 16:27:51 --- join: proteusguy (~proteus-g@107.77.244.34) joined #forth 16:27:52 --- mode: ChanServ set +v proteusguy 16:38:07 --- quit: APic (Ping timeout: 255 seconds) 16:47:03 --- quit: MickyW (Quit: Leaving. Have a nice time.) 16:52:35 --- quit: true-grue (Read error: Connection reset by peer) 18:21:53 --- join: APic (apic@apic.name) joined #forth 20:04:49 --- quit: jedb (Ping timeout: 276 seconds) 20:14:11 --- quit: karswell (Read error: Connection reset by peer) 20:14:23 --- join: karswell` (~user@186.91.199.146.dyn.plus.net) joined #forth 20:21:39 --- join: jedb (~jedb@119.77.75.137) joined #forth 20:57:49 --- join: gravicappa (~gravicapp@h62-133-162-25.dyn.bashtel.ru) joined #forth 21:54:09 --- quit: mark4 (Ping timeout: 260 seconds) 22:15:42 --- join: GeDaMo (~GeDaMo@212.225.125.110) joined #forth 23:59:59 --- log: ended forth/17.07.08