00:00:00 --- log: started forth/13.05.22 00:07:18 --- join: epicmonkey (~epicmonke@188.134.41.113) joined #forth 00:30:52 --- quit: epicmonkey (Ping timeout: 256 seconds) 00:39:56 --- quit: Nisstyre-laptop (Ping timeout: 256 seconds) 01:36:15 --- join: nighty^ (~nighty@tin51-1-82-226-147-104.fbx.proxad.net) joined #forth 01:37:26 --- join: epicmonkey (~epicmonke@host-224-58.dataart.net) joined #forth 01:38:31 --- quit: nighty^ (Read error: Operation timed out) 01:44:55 yunfan: just the outer / text interpreter of a Forth implementation. You'd be able to print it with decent size text. 01:48:37 impomatic: then which version of outer should i use? 01:48:39 --- quit: c00kiemon5ter (Ping timeout: 264 seconds) 01:48:44 my pyforth dont have outer :] 01:49:19 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 01:49:38 will check retro's outer 01:52:16 --- quit: c00kiemon5ter (Client Quit) 01:53:26 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 01:55:51 --- join: nighty^ (~nighty@tin51-1-82-226-147-104.fbx.proxad.net) joined #forth 02:00:40 --- quit: impomatic (Ping timeout: 252 seconds) 02:03:49 oop gforth's directory is similar with linux kernel's 02:32:54 --- join: skasio_ (~skasio@ppp118-209-4-42.lns20.mel4.internode.on.net) joined #forth 02:35:05 --- quit: skasio (Ping timeout: 248 seconds) 04:24:39 --- quit: skasio_ (Quit: Leaving) 04:33:59 yunfan: http://forth.pastebin.ca/2379974 04:34:37 As he says, it glosses over a *lot* of detail, but it outlines the idea pretty well. 04:37:50 --- join: skasio (~skasio@ppp118-209-4-42.lns20.mel4.internode.on.net) joined #forth 04:45:16 --- join: dessos_ (~dessos@c-174-60-176-249.hsd1.pa.comcast.net) joined #forth 04:45:16 --- quit: dessos (Read error: Connection reset by peer) 04:46:02 or another option: http://forth.pastebin.ca/2379984 04:46:49 How 'bout DeCSS in Forth? :D 04:52:07 :) 04:54:21 * ttmrichter has fond memories of wearing about eight different "illegal T-shirts" with DeCSS in a variety of languages and formats. 05:03:26 --- quit: goingretro (Ping timeout: 256 seconds) 05:07:50 --- join: goingretro (~kbmaniac@31.51.110.48) joined #forth 06:35:34 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 09:06:13 --- join: ncv (~quassel@79.114.115.93) joined #forth 09:06:13 --- quit: ncv (Changing host) 09:06:13 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 09:38:50 --- quit: epicmonkey (Ping timeout: 256 seconds) 09:39:34 --- join: mtm (~mtm@c-76-102-52-34.hsd1.ca.comcast.net) joined #forth 09:53:26 --- join: _spt_ (~steven@host-92-12-219-221.as43234.net) joined #forth 09:53:26 --- quit: _spt_ (Changing host) 09:53:26 --- join: _spt_ (~steven@unaffiliated/-spt-/x-5624824) joined #forth 10:49:44 --- join: epicmonkey (~epicmonke@188.134.41.113) joined #forth 11:22:33 --- quit: fantazo (Ping timeout: 248 seconds) 11:35:17 --- nick: dessos_ -> dessos 11:44:51 --- join: Mat2 (~claude@91-65-144-133-dynip.superkabel.de) joined #forth 11:45:02 hello 11:47:30 ttmrichter: I've heard you plan to develop a GA144 based board ? 12:02:55 --- quit: _spt_ (Ping timeout: 260 seconds) 12:06:53 --- join: _spt_ (~steven@host-92-12-230-183.as43234.net) joined #forth 12:06:53 --- quit: _spt_ (Changing host) 12:06:53 --- join: _spt_ (~steven@unaffiliated/-spt-/x-5624824) joined #forth 12:12:24 --- join: Nisstyre-laptop (~yours@oftn/member/Nisstyre) joined #forth 12:35:12 --- join: nighty- (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 12:38:29 --- join: Vuokko_ (vuolasah@mustatilhi.cs.tut.fi) joined #forth 12:42:53 --- quit: Vuokko (*.net *.split) 12:42:53 --- quit: nighty-_ (*.net *.split) 12:45:36 --- join: kumul (~mool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 13:18:49 --- join: Onionnion (~ryan@adsl-68-254-163-214.dsl.milwwi.ameritech.net) joined #forth 13:38:12 --- join: ASau` (~user@p5797FB60.dip0.t-ipconnect.de) joined #forth 13:41:16 --- quit: ASau (Ping timeout: 252 seconds) 13:46:07 --- quit: Nisstyre-laptop (Quit: Leaving) 14:11:44 --- quit: _spt_ (Quit: bye) 14:26:56 --- nick: ASau` -> ASau 14:54:14 --- quit: ncv (Remote host closed the connection) 15:04:50 --- quit: kumul (Quit: Leaving) 15:23:12 --- quit: Mat2 (Quit: Verlassend) 15:43:45 --- quit: Onionnion (Quit: Leaving) 16:14:05 --- quit: epicmonkey (Ping timeout: 256 seconds) 16:38:51 --- quit: nighty^ (Read error: Connection reset by peer) 16:40:25 --- nick: Vuokko_ -> Vuokko 17:03:17 --- quit: mtm (Quit: Leaving...) 17:14:34 --- join: RodgerTheGreat (~rodger@50-198-177-185-static.hfc.comcastbusiness.net) joined #forth 17:15:55 --- join: RodgerTheGreat_ (~rodger@50-198-177-185-static.hfc.comcastbusiness.net) joined #forth 17:15:55 --- quit: RodgerTheGreat (Read error: Connection reset by peer) 17:15:56 --- nick: RodgerTheGreat_ -> RodgerTheGreat 17:20:43 --- quit: RodgerTheGreat (Ping timeout: 260 seconds) 17:23:37 --- join: RodgerTheGreat (~rodger@50-198-177-185-static.hfc.comcastbusiness.net) joined #forth 18:14:14 --- join: Nisstyre-laptop (~yours@oftn/member/Nisstyre) joined #forth 18:34:57 --- nick: Nisstyre-laptop -> Nisstyre 19:39:10 tathi: checked those two paste, seem too loong for being printed on Tee 19:39:31 but i could take one word's definition for printing 19:41:31 and i need a better looking colorscheme, my Tee would be black as background color 19:48:32 --- quit: kulp (Ping timeout: 245 seconds) 19:55:43 --- join: kulp (~kulp@unaffiliated/kulp) joined #forth 20:07:56 can i get a critique on the "forthiness" of a fizzbuzz i did? 20:07:58 http://pastebin.com/M2RxUpZ9 20:08:17 wondering if there are substantially better ways, more forth idiomatic, etc. 20:09:40 for comparison, here is a fizzbuzz I wrote: http://hastebin.com/yabaqidafu.fs 20:10:07 I think that in general nested conditionals are undesirable 20:10:33 it's best if you have at most one control structure per factor 20:10:44 doesn't always work out that way but it's a goal 20:13:21 --- join: Onionnion (~ryan@adsl-68-254-163-214.dsl.milwwi.ameritech.net) joined #forth 20:13:42 bluekelp: does that help? 20:13:46 yeah, i also realized fizzbuzz? buzz? and fizz? differ only in the "magic number" but wasn't sure it warranted attempting to de-dup 20:13:52 looking at the code now 20:16:18 RodgerTheGreat: there's no way (other than vars?/etc) to push the strings "fizz" "buzz" on the stack -- to fully parameratize the fizz and buzz words to a common (mod0print) word, right? 20:16:39 it can be done but it's one of those diminishing returns things 20:17:51 stack shuffling starts to get a bit inconvenient, especially if you're using a typical forth which represents strings with a base,length pair 20:18:09 thx. the if/else ladder felt wrong - didn't occur to OR them - i like that 20:18:34 also note how I avoid an else in my "fizz" and "buzz" words 20:19:08 whenever you find yourself doing "if ... true else false then" instead do "dup if ... then" 20:19:22 you already have that flag, y'know? 20:19:40 ah, the dup after 'divides?' - nice 20:21:58 ok, back to envying jonesforth for its simplicity. compared to uforth86 it's a work of art ;) 20:48:11 --- quit: skasio (Remote host closed the connection) 20:48:29 --- join: skasio (~skasio@ppp118-209-4-42.lns20.mel4.internode.on.net) joined #forth 20:54:11 i am just wonder if people could use forth implementing a networkd card driver which support libev like api and still got hight performance 21:37:07 --- quit: Onionnion (Quit: Leaving) 21:44:57 --- quit: RodgerTheGreat (Quit: RodgerTheGreat) 22:26:29 --- join: Indecipherable (~Indeciphe@41.29.91.16) joined #forth 22:31:07 --- quit: Indecipherable (Client Quit) 23:37:41 --- quit: kulp (Ping timeout: 245 seconds) 23:40:51 --- join: kulp (~kulp@unaffiliated/kulp) joined #forth 23:59:59 --- log: ended forth/13.05.22