00:00:00 --- log: started forth/11.05.27 00:45:43 --- quit: DocPlatypus (Ping timeout: 260 seconds) 00:50:51 --- quit: ttmrichter (Quit: No wonder these puppets are always in a lousy mood.) 01:48:29 --- quit: jyfl987 (Ping timeout: 246 seconds) 01:56:16 --- join: jyfl987 (~jyf@221.221.174.94) joined #forth 01:59:39 a idea, is there any linux syscall implement by forth? 02:25:32 --- quit: xiaohao (Quit: Page closed) 02:39:49 --- quit: jyfl987 (Quit: Leaving.) 03:24:38 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 04:32:56 --- quit: ygrek (Ping timeout: 246 seconds) 04:53:02 --- join: TeruFSX (~quassel@71-210-136-53.mpls.qwest.net) joined #forth 05:26:04 --- join: MoALTz (~no@host-92-8-149-15.as43234.net) joined #forth 06:00:17 --- join: ttmrichter (~ttmrichte@111.173.97.210) joined #forth 06:44:08 --- join: cjbaird (~cjb@ppp121-44-23-149.lns20.syd6.internode.on.net) joined #forth 06:57:33 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 07:37:09 --- quit: MayDaniel (Read error: Connection reset by peer) 07:47:55 --- join: DocPlatypus (~skquinn@dsl253-084-031.hou1.dsl.speakeasy.net) joined #forth 07:59:55 --- quit: nighty__ (Quit: Disappears in a puff of smoke) 08:01:52 --- quit: Fox78 (Remote host closed the connection) 08:31:54 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 08:31:58 --- join: Snoopy_1611 (Snoopy_161@dslb-178-004-030-175.pools.arcor-ip.net) joined #forth 08:36:47 --- quit: cjbaird (Remote host closed the connection) 08:36:57 --- quit: ttmrichter (Quit: No wonder these puppets are always in a lousy mood.) 08:42:07 --- quit: Joseph__ (Ping timeout: 250 seconds) 09:02:54 --- quit: DocPlatypus (Ping timeout: 250 seconds) 09:08:49 --- quit: Snoopy_1611 () 09:15:54 --- quit: MayDaniel (Read error: Connection reset by peer) 09:19:34 --- join: DocPlatypus (~skquinn@dsl253-084-031.hou1.dsl.speakeasy.net) joined #forth 09:40:34 --- quit: DocPlatypus (Read error: Connection reset by peer) 10:06:39 --- join: DocPlatypus (~skquinn@dsl253-084-031.hou1.dsl.speakeasy.net) joined #forth 10:10:43 --- join: jyfl987 (~notedit@unaffiliated/yunfan) joined #forth 10:11:05 --- part: jyfl987 left #forth 10:27:42 --- quit: MoALTz (Ping timeout: 276 seconds) 11:15:24 --- join: xpololz (~tommy@50.80-203-124.nextgentel.com) joined #forth 11:16:16 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 11:28:35 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 13:05:51 --- quit: MayDaniel (Read error: Connection reset by peer) 13:20:25 --- quit: mur (Ping timeout: 240 seconds) 13:21:48 --- join: mur (~murrrrr@uiah.fi) joined #forth 13:43:27 --- quit: grai (Read error: Connection reset by peer) 13:45:12 --- join: grai (~grai@38.70.70.115.static.exetel.com.au) joined #forth 14:09:05 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 14:10:09 --- quit: TeruFSX (Read error: Operation timed out) 14:11:03 --- join: TeruFSX (~quassel@71-210-136-53.mpls.qwest.net) joined #forth 14:16:30 --- quit: ygrek (Ping timeout: 246 seconds) 14:48:57 --- quit: TeruFSX (Read error: Connection reset by peer) 15:12:40 --- quit: MayDaniel (Read error: Connection reset by peer) 15:34:14 --- join: Fox78 (~fox@123.121.81.11) joined #forth 16:19:08 --- quit: Fox78 (Remote host closed the connection) 16:19:49 --- join: ttmrichter (~ttmrichte@111.173.97.210) joined #forth 16:27:12 --- join: Joseph__ (~Joseph@cpe-98-155-76-109.san.res.rr.com) joined #forth 18:10:43 i've been clearing the stack by typing in an undefined word 18:11:03 is there another way to do it (in gforth or pfe) without generating an error message? 18:11:32 i came up with this: : 0sp depth dup 0 > if 0 do drop loop then ; 18:11:56 but there's probably a better way.. right? 20:00:31 --- quit: ttmrichter (Read error: Connection timed out) 20:00:56 --- join: ttmrichter (~ttmrichte@111.173.97.210) joined #forth 20:07:58 --- quit: cataska (Quit: leaving) 20:18:03 --- join: cataska (~cataska@210.64.6.233) joined #forth 21:47:06 There're "abort" and "quit". 21:47:53 No standard way to reset single stack. 21:49:11 Your definition is dangerous, actually. 21:49:31 It works only if your system catches undeflows somehow. 21:55:14 --- join: cjbaird (~cjb@ppp121-44-23-149.lns20.syd6.internode.on.net) joined #forth 22:15:59 --- join: roarde (~roarde@pdpc/supporter/active/roarde) joined #forth 22:18:45 --- join: AndroUser (~androirc@pool-108-38-79-155.lsanca.fios.verizon.net) joined #forth 23:31:20 ASau: could you elaborate? i'm brand new to forth, and don't understand what that definition has to do with underflows 23:34:37 Your "0sp" doesn't handle stack underflow gracefully. 23:35:37 When you have underflowed, it's better not to clutter it further. 23:37:37 --- join: MoALTz (~no@92.8.149.15) joined #forth 23:38:00 There're some chances that "quit" resets stacks more gracefully. 23:39:23 but i don't understand where the stack underflow would come from when i run sp0 23:39:52 What if it happened before? 23:40:00 Otherwise why would you want to reset stack? 23:40:31 i'd want to reset the stack because i put some stuff on there to test it, and want to get rid of it 23:40:41 or because some other word left too much on the stack by accident 23:41:02 Hm. 23:41:07 Just run "abort". 23:41:09 but i'm not sure how an underflow from before sp0 ran would affect sp0 itself 23:41:13 That's what you do effectively. 23:41:33 sure, i don't mind using abort 23:41:51 (Also "sp0" is traditional name for a variable holding address of stack bottom.) 23:42:12 but it will reset all the stacks, not just the procedural stack, right? 23:42:37 "abort"? Right. 23:43:09 But if you reset any stack manually, you're in some weird state already. 23:43:32 (I know that there can exist some funky cases.) 23:44:09 true 23:44:18 and i see that i misnamed sp0 23:44:21 meant to call it 0sp 23:44:43 : discard 0 ?do drop loop ; 23:45:04 You'll need it in elaborate programs anyway. 23:45:25 got the name 0sp from here: http://www.softsynth.com/pforth/pf_tut.php 23:45:52 Ah. 23:46:05 pForth insists on some stupid design decisions. 23:46:42 It is rather archaic and stagnant. 23:47:04 (Even by Forth standards.) 23:47:12 good to know 23:47:28 i wasn't actually going to use pforth 23:47:35 just checking out their forth tutorial 23:47:42 which said: "Between examples, you will probably want to clear the stack. If you enter 0SP, pronounced "zero S P", then the stack will be cleared." 23:48:03 and since that didn't work, and i couldn't find a replacement, i set out to write my own 23:48:13 but i'll just use abort from now on 23:48:17 Which Forth do you use? 23:48:25 gforth and pfe 23:48:56 pfe seems to have nice embedded docs, so i tend to mostly use that 23:48:59 --- quit: roarde (Quit: Leaving) 23:49:11 i like how i can just type "help foo" and get a bit of info on the word 23:49:13 --- quit: shachaf (Ping timeout: 248 seconds) 23:49:43 gforth has "clearstack" and "clearstacks" 23:49:49 for gforth i have to dig through the index of their web page 23:49:58 Use info. 23:50:30 pfe has "clearstack". 23:51:01 i'm getting "undefined word" when i type "info" in both gforth and pfe 23:51:19 It is common tool. 23:51:24 oh 23:51:26 It isn't forth-only. 23:51:41 you mean gnu info? that runs from the shell? 23:52:26 i've done that.. but i still prefer pfe's embedded help command 23:52:35 since i don't have to switch away from forth to use it 23:52:46 and i can also immediately zero in on the command i want help on 23:52:51 rather than searching through an index 23:53:04 I use Emacs, and I don't have to switch at all. 23:54:24 i'm using vim.. and its forth integration is non-existant 23:54:45 Well... Don't use it. 23:54:57 Use Emacs, and you'll have enough integration. 23:55:02 i'd use emacs if i knew it well enough 23:55:05 but i don't 23:55:40 If you can use keypad, you know Emacs well enough. 23:55:58 i'm just much more comfortable editing in vim 23:56:12 when using emacs i feel crippled.. even with viper and vimpulse 23:56:25 Don't use neither viper nor vimpulse. 23:56:35 then it'd be even worse for me 23:56:42 i need my modal editing :) 23:57:08 It's rather weird to look at people arguing that modal editing isn't crippled. 23:57:51 --- join: shachaf (~shachaf@208.69.183.87) joined #forth 23:58:02 well... let's just say it's a matter of taste.. 23:58:08 before this turns in to an editor war.. :) 23:58:11 It isn't matter of taste. 23:58:30 There exists objective measure. 23:59:59 --- log: ended forth/11.05.27