00:00:00 --- log: started forth/12.03.09 00:10:28 --- join: ttmrichter (~ttmrichte@221.234.38.23) joined #forth 00:10:28 --- mode: ChanServ set +v ttmrichter 00:18:56 --- quit: cataska (Quit: leaving) 00:30:37 --- join: cataska (~cataska@210.64.6.233) joined #forth 00:30:37 --- mode: ChanServ set +v cataska 00:35:43 --- join: ghavino_ohyeah (6c0ddab8@gateway/web/freenode/ip.108.13.218.184) joined #forth 00:35:43 --- mode: ChanServ set +v ghavino_ohyeah 00:35:49 forth forth bo berth!!! 01:51:47 --- quit: MrBusiness (Quit: Leaving) 02:03:59 lol 02:06:48 forth forth bo borth 02:06:55 any forthers in here? 02:09:47 yes, but most are asleep I think 02:22:46 hey doc, do you find forth useful in normal server datacenter operations or more for embeded systems? 02:35:17 --- quit: clog (Ping timeout: 265 seconds) 02:35:17 --- log: stopped forth/12.03.09 02:35:23 --- log: started forth/12.03.09 02:35:23 --- join: clog (~nef@bespin.org) joined #forth 02:35:23 --- topic: 'Forth Programming | logged by clog at http://bit.ly/91toWN | links: qr.net/gforth isforth.com forthfreak.net qr.net/ans_standard | Buy forth chips from www.greenarraychips.com | prize money for coding an efficient SHA-256 hashing algorithm for the chips, talk to docl or foucist' 02:35:23 --- topic: set by foucist!~foucist@ps14150.dreamhost.com on [Thu Jan 19 01:03:52 2012] 02:35:23 --- names: list (clog +ghavino_ohyeah +cataska +ttmrichter +nighty- +nighty +malyn +tschak__ +DocPlatypus +mark4 +mtm +DGASAU +segher +Nisstyre +karswell +ivan` +koisoke +shachaf +angstrom +kandinski +yiyus +KipIngram +newcup +crc +Inode +_phred +nottwo +dom96) 02:35:23 --- mode: ChanServ set +v clog 02:52:41 --- quit: ghavino_ohyeah (Quit: Page closed) 06:31:32 --- quit: koisoke (Quit: rebooting) 06:40:01 --- join: ttmrichter_ (~ttmrichte@221.234.38.23) joined #forth 06:40:01 --- mode: ChanServ set +v ttmrichter_ 06:40:23 --- quit: ttmrichter (Disconnected by services) 06:40:33 --- nick: ttmrichter_ -> ttmrichter 06:43:59 --- join: koisoke (xef4@epilogue.org) joined #forth 06:43:59 --- mode: ChanServ set +v koisoke 07:04:49 --- join: Kumul (~Kumul@adsl-72-50-67-191.prtc.net) joined #forth 07:04:49 --- mode: ChanServ set +v Kumul 08:12:13 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 08:12:13 --- mode: ChanServ set +v MayDaniel 08:17:19 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 08:17:19 --- mode: ChanServ set +v nighty^ 09:00:46 --- quit: ttmrichter (Quit: Leaving) 09:18:01 --- quit: karswell (Ping timeout: 245 seconds) 09:25:33 --- join: karswell (~coat@93-97-29-243.zone5.bethere.co.uk) joined #forth 09:25:33 --- mode: ChanServ set +v karswell 10:31:12 --- join: kulp (~kulp@unaffiliated/kulp) joined #forth 10:31:13 --- mode: ChanServ set +v kulp 11:33:34 how many forth implementors in here, by curiosity ? 11:39:33 --- part: Kumul left #forth 11:43:29 I've implemented a forth dialect (retro) and mark4 wrote isForth 11:45:39 ah. i'm a forth newbie, getting started on an implementation on an architecture of my own design 11:46:10 so although it doesn't look particularly high-traffic i might hang around and ask beginner questions from time to time if it isn't too painful for you :) 12:00:19 --- join: tschak_ (~tschak@vpn.touchtunes.com) joined #forth 12:00:19 --- mode: ChanServ set +v tschak_ 12:03:37 --- quit: tschak__ (Ping timeout: 260 seconds) 12:07:29 --- quit: nighty^ (Remote host closed the connection) 12:29:00 feel free to ask. answers will come eventually :) 12:34:30 man, the return stack words do make some things a lot simpler. 12:35:23 am noticing i'm having to THINK a lot more, when I approach how to write a chunk of code, otherwise it gets messy really quickly 12:36:17 --- quit: MayDaniel (Read error: Connection reset by peer) 12:44:38 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 12:44:39 --- mode: ChanServ set +v nighty^ 13:12:57 --- join: adasfdasf (~adasfdasf@177.32.89.101) joined #forth 13:13:00 --- mode: ChanServ set +v adasfdasf 13:13:13 --- quit: adasfdasf (Client Quit) 15:13:00 --- join: Kumul (~Kumul@adsl-72-50-67-191.prtc.net) joined #forth 15:13:01 --- mode: ChanServ set +v Kumul 17:08:46 --- join: MrBusiness (~MrBusines@184.99.7.19) joined #forth 17:08:46 --- mode: ChanServ set +v MrBusiness 17:20:02 --- quit: nighty^ (Remote host closed the connection) 17:23:07 --- join: I440r (~zhiming@173-167-173-233-illinois.hfc.comcastbusiness.net) joined #forth 17:23:07 --- mode: ChanServ set +v I440r 17:27:13 --- quit: Inode (Ping timeout: 252 seconds) 18:13:02 --- quit: karswell (Ping timeout: 246 seconds) 18:25:04 --- join: ttmrichter (~ttmrichte@221.234.38.23) joined #forth 18:25:05 --- mode: ChanServ set +v ttmrichter 18:37:48 --- quit: DocPlatypus (Quit: Leaving) 19:52:24 --- join: bytbox (~s@129.2.129.225) joined #forth 19:52:24 --- mode: ChanServ set +v bytbox 19:52:26 --- part: bytbox left #forth 20:16:56 --- quit: Kumul (Quit: gone) 21:59:40 --- join: tschak__ (~tschak@pool-96-226-11-78.dllstx.fios.verizon.net) joined #forth 21:59:40 --- mode: ChanServ set +v tschak__ 22:03:41 --- quit: tschak_ (Ping timeout: 246 seconds) 22:30:46 --- join: DocPlatypus (~skquinn@108-75-59-67.lightspeed.hstntx.sbcglobal.net) joined #forth 22:30:46 --- mode: ChanServ set +v DocPlatypus 23:45:30 --- quit: malyn (Read error: Connection reset by peer) 23:45:34 --- join: malyn_ (~malyn@unaffiliated/malyn) joined #forth 23:45:34 --- mode: ChanServ set +v malyn_ 23:46:30 --- nick: malyn_ -> malyn 23:48:54 --- quit: DocPlatypus (Quit: Leaving) 23:50:30 --- quit: I440r (Remote host closed the connection) 23:59:59 --- log: ended forth/12.03.09