00:00:00 --- log: started forth/10.04.16 00:05:01 --- join: ASau` (~user@77.246.231.195) joined #forth 00:57:41 --- join: sunwukong (~vukung@business-80-99-161-225.business.broadband.hu) joined #forth 01:03:12 --- join: kar8nga (~kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 01:40:10 --- quit: ASau (Ping timeout: 276 seconds) 01:47:18 --- quit: Snoopy_1611 () 01:48:52 --- quit: sunwukong (Remote host closed the connection) 01:54:38 --- quit: nighty__ (Quit: Disappears in a puff of smoke) 02:59:54 --- quit: kar8nga (Remote host closed the connection) 03:59:26 --- join: tgunr_ (~tgunr@2001:0:53aa:64c:0:3192:bd06:59f4) joined #forth 04:04:15 --- join: kar8nga (~kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 06:14:57 --- quit: gogonkt (Ping timeout: 260 seconds) 06:17:01 --- join: gogonkt (~info@218.13.63.42) joined #forth 06:28:33 --- join: saper_ (saper@akson.sgh.waw.pl) joined #forth 06:33:22 --- quit: saper (*.net *.split) 06:50:34 --- quit: mathrick (Remote host closed the connection) 06:52:26 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 07:43:32 --- join: zashi (~mhiles@nat/ibm/x-wbojnwqqchtaojch) joined #forth 07:44:26 Ah, just learning forth. I've got a detailed glossary but can't figure out how (or if) you can get a count of elements in the stack. 07:45:16 depth 07:45:25 :D thank you. 07:48:50 --- quit: ygrek (Ping timeout: 245 seconds) 07:49:22 --- quit: Deformative (Ping timeout: 264 seconds) 07:58:42 --- quit: ASau` (Quit: off) 08:29:32 --- join: Snoopy_1611 (Snoopy_161@dslb-084-059-107-156.pools.arcor-ip.net) joined #forth 08:29:56 --- join: Snoopy_1711 (Snoopy_161@dslb-084-059-206-165.pools.arcor-ip.net) joined #forth 08:33:54 --- quit: Snoopy_1611 (Ping timeout: 258 seconds) 08:40:08 --- join: Snoopy_1611 (Snoopy_161@dslb-088-068-192-166.pools.arcor-ip.net) joined #forth 08:43:11 --- join: TR2N (email@89.180.216.232) joined #forth 08:44:30 --- quit: Snoopy_1711 (Ping timeout: 260 seconds) 08:57:37 --- quit: gnomon (Ping timeout: 276 seconds) 09:10:04 --- quit: crc (Ping timeout: 246 seconds) 09:12:04 --- join: crc (~charlesch@184.77.185.20) joined #forth 09:17:54 --- join: ASau (~user@83.69.227.32) joined #forth 09:21:24 --- nick: saper_ -> saper 09:21:38 --- quit: saper (Changing host) 09:21:38 --- join: saper (saper@wikipedia/saper) joined #forth 09:21:53 --- join: madwork (~madgarden@204.138.110.15) joined #forth 09:52:19 --- join: gnomon_ (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 10:05:05 --- quit: madwork (Ping timeout: 245 seconds) 10:09:33 --- join: dmsh (~dmsh@ppp91-77-133-193.pppoe.mtu-net.ru) joined #forth 10:10:13 --- join: madwork (~madgarden@204.138.110.15) joined #forth 10:10:16 --- part: dmsh left #forth 10:44:00 --- quit: kar8nga (Remote host closed the connection) 10:49:05 I feel absolutely retarded that I can't figure this out. 10:49:06 I run gforth fizzbuzz.fs; and get 10:49:06 fizzbuzz.fs:3: Interpreting a compile-only word 10:49:06 >>>do<<< 10:51:42 You cannot use "do" in interpreting mode. 10:52:14 That much I realize :/ I think I found what I need to explain what I'm missing. 10:52:14 "do" and the company are compile-only in gforth. 10:52:19 I need to change my "state" ? 10:52:39 First you are to explain what you're doing and what you 10:52:39 want to accomplish. 10:53:23 I don't see your fizzbuzz.fs and thus I cannot tell what is wrong. 10:55:43 I think I'm reading what I need to. I'll spare you my idiocy until I'm sure I can't figure this out. 11:07:30 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 11:09:43 --- nick: gnomon_ -> gnomon 11:33:32 --- join: mark4 (~mark4@baldr.openesque.com) joined #forth 11:33:36 --- nick: mark4 -> I440r 11:57:50 Yes, that word expects to fire when compiling. 11:58:24 --- quit: tgunr_ (Read error: Connection reset by peer) 11:58:31 I don't know for sure about gforth, but in most "traditional" installations it will also leave some compile time info on the stack that gets checked by the LOOP that's supposed to come later. 11:58:36 Part of compile time error checking. 11:59:40 No, it doesn't. 11:59:55 It is simply allowed that it doesn't work when interpreted. 11:59:57 DO doesn't really compile anything, does it? Just saves info for LOOP or +LOOP to use (error checking and back-target for the branch)? 12:00:17 It does compile. 12:00:41 It has to save initial value and limit somehow. 12:07:17 --- nick: mathrick -> dumbfoone 12:09:39 --- nick: dumbfoone -> mathrick 12:10:19 --- quit: Quartus` (Ping timeout: 246 seconds) 13:06:34 --- join: GoNoGo (~GoNoGo@2a01:e35:2ec5:dd70:7deb:c036:6f05:65aa) joined #forth 13:10:45 --- quit: I440r (Quit: Lost terminal) 14:04:35 --- quit: GoNoGo (Quit: ChatZilla 0.9.86 [Firefox 3.6.3/20100401080539]) 14:09:17 --- quit: ygrek (Remote host closed the connection) 14:27:47 --- join: TR2N` (email@89-180-216-232.net.novis.pt) joined #forth 14:28:19 --- quit: TR2N (Disconnected by services) 14:28:24 --- nick: TR2N` -> TR2N 16:51:24 --- join: tgunr (~tgunr@cust-66-249-166-11.static.o1.com) joined #forth 17:47:44 --- join: fhoahf30914 (~Gla@200-55-110-251.dsl.prima.net.ar) joined #forth 17:47:45 --- part: fhoahf30914 left #forth 18:34:21 --- mode: ChanServ set +o crc 19:07:21 --- quit: segher (Quit: This computer has gone to sleep) 19:15:15 --- quit: probonono (Ping timeout: 240 seconds) 19:17:01 --- join: probonono (~User@unaffiliated/probonono) joined #forth 19:49:17 --- join: Deformative (~joe@c-76-112-68-135.hsd1.mi.comcast.net) joined #forth 21:37:35 --- join: Kumul (~Kumool@66-50-79-232.prtc.net) joined #forth 21:52:06 --- quit: Kumul (Quit: Gone) 23:23:05 --- part: TR2N left #forth 23:33:23 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 23:59:59 --- log: ended forth/10.04.16