00:00:00 --- log: started forth/14.06.09 00:08:45 --- quit: mnemnion (Read error: Connection reset by peer) 00:09:15 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 01:12:00 --- quit: mnemnion (Remote host closed the connection) 02:25:51 --- join: pvt_petey (~pvt_petey@cpc11-colc6-2-0-cust131.7-4.cable.virginm.net) joined #forth 02:30:44 --- join: true-grue (~grue@95-25-84-251.broadband.corbina.ru) joined #forth 02:37:20 --- join: true-grue_ (~grue@95-25-84-251.broadband.corbina.ru) joined #forth 02:44:30 --- quit: true-grue (*.net *.split) 03:31:09 --- quit: MrMobius (Disconnected by services) 03:31:22 --- join: MrM0bius (~Joey@194.176.111.170) joined #forth 03:38:52 --- quit: pvt_petey () 04:24:42 --- quit: DGASAU (Ping timeout: 252 seconds) 04:26:21 --- join: DGASAU (~user@p50993595.dip0.t-ipconnect.de) joined #forth 04:39:42 --- join: MrMobius (~Joey@91.192.67.239) joined #forth 04:42:28 --- quit: MrM0bius (Ping timeout: 246 seconds) 05:08:57 --- quit: backer_ (Ping timeout: 240 seconds) 05:10:25 --- join: backer (~backer@user-387h3hl.cable.mindspring.com) joined #forth 05:14:46 --- quit: karswell (Ping timeout: 276 seconds) 05:15:38 --- join: karswell` (~user@87.112.34.104) joined #forth 05:33:58 --- quit: backer (Remote host closed the connection) 05:34:09 --- join: backer (~backer@user-387h3hl.cable.mindspring.com) joined #forth 05:37:35 --- quit: djinni (Quit: ERC Version 5.3 (IRC client for Emacs)) 05:41:46 --- join: djinni (~djinni@192.241.198.49) joined #forth 06:01:15 --- join: ASau` (~user@46.114.15.93) joined #forth 06:03:57 --- quit: ASau (Ping timeout: 240 seconds) 06:04:41 --- nick: ASau` -> ASau 07:13:08 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 07:21:02 --- quit: MrMobius (Read error: Connection reset by peer) 07:23:08 --- join: MrMobius (~Joey@91.192.67.239) joined #forth 08:04:04 --- quit: MrMobius (Ping timeout: 246 seconds) 08:10:16 --- quit: cataska (Ping timeout: 276 seconds) 08:17:05 --- join: cataska (~cataska@118-163-69-1.HINET-IP.hinet.net) joined #forth 08:28:55 --- quit: cataska (Ping timeout: 252 seconds) 08:42:57 --- join: kumul (~mool@adsl-72-50-85-7.prtc.net) joined #forth 09:48:26 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 10:15:28 --- join: kumool (~mool@adsl-72-50-86-254.prtc.net) joined #forth 10:16:27 --- quit: kumool (Client Quit) 10:16:53 --- join: kumool (~mool@adsl-72-50-86-254.prtc.net) joined #forth 10:19:20 --- quit: kumul (Ping timeout: 260 seconds) 10:45:48 --- quit: Zarutian (Quit: Zarutian) 11:31:52 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 12:23:00 --- join: _spt_ (~Jaat@host-92-12-215-105.as43234.net) joined #forth 12:23:14 --- quit: _spt_ (Changing host) 12:23:14 --- join: _spt_ (~Jaat@unaffiliated/-spt-/x-5624824) joined #forth 12:37:03 --- join: ehaliewicz (~user@50-0-50-2.dsl.dynamic.sonic.net) joined #forth 12:57:09 --- nick: daowee_ -> daowee 13:22:25 --- join: mnemnion_ (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 13:26:11 --- quit: mnemnion (Ping timeout: 276 seconds) 13:37:38 --- quit: goingretro (Ping timeout: 240 seconds) 13:37:53 --- join: goingretro (~kbmaniac@host86-157-30-139.range86-157.btcentralplus.com) joined #forth 13:38:19 --- quit: Zarutian (Quit: Zarutian) 13:42:00 --- quit: true-grue_ (Read error: Connection reset by peer) 13:52:00 --- join: jimt_ (~jim@ad004182.dynamic.ppp.asahi-net.or.jp) joined #forth 13:54:30 --- quit: jimt (Ping timeout: 264 seconds) 14:01:03 --- join: Mat3 (~Mat@91-64-127-6-dynip.superkabel.de) joined #forth 14:01:05 hello 14:02:23 hey Mat3 14:02:49 hello bluekelp 14:25:59 --- quit: Mat3 (Ping timeout: 276 seconds) 14:36:10 --- quit: mnemnion_ (Read error: Connection reset by peer) 14:36:40 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 15:33:42 --- quit: joneshf-laptop (Remote host closed the connection) 15:34:50 --- join: joneshf-laptop (~joneshf@98.255.30.38) joined #forth 15:41:15 --- quit: _spt_ (Quit: the Jupiter ACE has lost connection) 15:53:15 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 16:05:17 https://dl.dropboxusercontent.com/u/3581058/forth-compiler.gif finally got the compiler to work 16:19:00 --- quit: daowee (Ping timeout: 252 seconds) 16:19:03 cool 16:20:49 --- join: daowee (~daowee@m90-141-144-151.cust.tele2.se) joined #forth 16:48:54 --- join: saml_ (~saml@pool-71-190-2-70.nycmny.east.verizon.net) joined #forth 16:49:13 --- quit: nisstyre (Quit: WeeChat 0.4.3) 16:49:39 --- quit: kumool (Ping timeout: 276 seconds) 16:49:49 --- join: nisstyre (yourstruly@oftn/member/Nisstyre) joined #forth 17:03:22 --- quit: Zarutian (Ping timeout: 252 seconds) 17:09:07 --- join: kumool (~mool@adsl-72-50-86-254.prtc.net) joined #forth 17:09:52 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 17:20:57 --- nick: jimt_ -> jimt 17:21:29 --- quit: Zarutian (Ping timeout: 260 seconds) 17:26:28 --- join: Zarutian (~zarutian@194-144-84-110.du.xdsl.is) joined #forth 19:51:25 --- quit: saml_ (Quit: Leaving) 20:26:30 --- quit: Zarutian (Quit: Zarutian) 20:30:35 --- quit: mnemnion (Read error: Connection reset by peer) 20:31:06 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 20:35:25 what's the most common notation for return stack effects? 20:35:28 for comments, i mean 20:35:53 i guess i could just say r: ( ) 21:14:30 i think i've seen "dual" stack effect comments - one for data and one for return 21:15:01 though generally a word touches only one (but not always) so as long as it is specified should be fine 21:17:14 --- join: MrMobius (~Joey@91.192.67.235) joined #forth 21:20:04 Under what circumstances is having a return stack effect that isn't ( -- ) desirable? 21:20:27 * ttmrichter guesses at tasking systems or exception handling? 21:22:22 a few - like crashing your cpu :) 21:27:13 --- quit: kumool (Quit: Leaving) 21:37:41 well, why would you have a return stack if you don't want return stack effects? 21:37:48 they should be used sparingly of course 21:38:15 ehaliewicz: Wouldn't the *name* of the return stack be a clue as to why you have one? 21:38:51 So what is the viable use case for having return stack effects? 21:38:57 Is it non-local transfer of control? 21:39:03 sure, that works 21:51:26 * ASau points that there're a lot of words that don't have ( r: -- ) effect, none of them have any relation to non-local transfer of control. 22:17:37 ASau: So could you give some examples? 22:23:48 Sure. 22:24:20 >r r> r@ 2>r 2r> 2r@ and all the rest have absolutely no relation to non-local transfer of control. 22:28:33 OK, fair enough. 22:29:23 Aside from words, however, devoted to manipulating the return stack (which is a bit tautological) , what is the value of having return stack effects on words? 22:29:39 When would someone writing their own word use a return stack effect that's not ( -- )? 22:52:55 Any time one needs temporary data that are hard to keep on data stack. 22:53:01 * ASau shrugs. 22:53:38 In all practical cases return stack is addressable. 23:52:40 --- quit: ASau (Ping timeout: 240 seconds) 23:59:59 --- log: ended forth/14.06.09