00:00:00 --- log: started forth/04.02.27 00:17:31 --- quit: Herkamire ("Kronk out") 00:18:48 --- quit: slava (Connection reset by peer) 00:21:59 --- join: slava (~slava@CPE0080ad77a020-CM.cpe.net.cable.rogers.com) joined #forth 02:10:24 --- quit: proteusguy ("Leaving") 03:26:04 --- join: qFox (~C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 03:39:05 --- quit: warpzero (Read error: 110 (Connection timed out)) 04:58:46 --- join: networm (~networm@L0632P22.dipool.highway.telekom.at) joined #forth 04:59:19 Dobryjj vecher! 05:00:26 --- quit: hovil ("Leaving") 05:50:52 --- join: KOHTPA (~asau@158.250.48.196) joined #forth 05:50:53 --- quit: ASau (Read error: 104 (Connection reset by peer)) 05:51:16 --- nick: KOHTPA -> ASau 06:34:04 --- quit: ASau (Read error: 54 (Connection reset by peer)) 06:37:40 --- join: warpzero (~warpzero@dsl.142.mt.onewest.net) joined #forth 07:32:59 --- join: ASau (~asau@158.250.48.196) joined #forth 07:33:20 Privet 07:33:26 Privet! 07:36:50 KONTPA - the Konami game? :) 07:37:54 --- quit: networm ("Client exiting") 07:39:35 It was a joke of my father's friend. 07:41:03 He called everyone disagreeing "counter-revolutioner." "Contra" to be concise. 07:42:33 Hehe 08:46:25 I've made memory dumped utility in 1 screen. 08:46:37 ...memory dumping... 08:46:48 Does anyone need? 09:09:15 --- join: Herkamire (stjohns@h000094d30ba2.ne.client2.attbi.com) joined #forth 09:15:41 Dobryjj vecher! 09:17:43 ASau: good noon ;) 09:19:11 Do you need 1 screen mem. dump utility? 09:19:29 Pretty printing included. 09:22:16 ASau: huh? 09:22:59 I needed one for debugging purposes, so I've written it. 09:23:22 what is it dumping? 09:23:30 the text from gnu screen? 09:23:38 Hex dump. 09:24:00 XX XX XX XX - XX XX XX XX - ... 09:24:02 what data? the frame buffer? 09:24:15 Any memory block. 09:24:35 16-byte alignment is made auto-magically. 09:24:49 ASau: I see. what forth? 09:25:32 It seems, that it should work in any classical enough forth. 09:27:59 ASau: I'll take a look. 09:28:40 I don't need it right now, but I want to have a few more forth code examples on my website if you don't mind 09:28:46 (can I make it public domain?) 09:29:31 --- join: Nutssh (~Foo@gh-1081.gh.rice.edu) joined #forth 09:31:32 Consider it is free to reproduce. 11:03:00 hi 11:03:44 Hi slava 11:08:06 Privet! 11:22:48 Is there a standard a<=x<=b ( x a b -- ? ) word? 11:23:16 "Standard" means commonly used. 11:24:35 how about using math notation for intervals: [] is a<=x<=b, () is a Not a bad idea. 11:25:05 Hm. 11:25:16 ?[] for my case? 11:25:17 I've never seen any "standard" word for that anyway. 11:25:44 Or []? ? 11:25:49 ASau, what are you coding in forth? 11:26:19 I migrate to forth with my research works. 11:26:38 cool 11:26:43 what forth? 11:27:07 Consider it is FIG-Forth. 11:27:19 It differs a little. 11:31:00 is 850 words considered a large program? 11:31:48 In my world, yes. 11:31:49 My Forth core is about 200 words. 11:32:30 So 850 is about four times as large. 11:32:45 well not the language itself but the program 11:33:22 It is pretty large. 11:33:44 imo the number of words says little about how big it is 11:34:14 maybe you have alot of words because you've optimized alot, increasing the number of words, but decreasing teh size of the code 11:34:26 Consider 5 lines per word average. 11:34:28 btw, i'm "back", brace for impact ;) 11:34:37 No. 11:34:44 2--3 lines. 11:35:26 ASau, i have 2-3 lines per word average 11:36:25 Hm. 11:36:55 Intervals: "x IN a b []" syntax. 11:37:33 "x a b IN []" is also accepted as syn. 11:38:26 No. IN overlaps core word. 11:39:21 But idea seems good enough. 11:43:05 TeX-like idea: \in[] \in() \in[) 11:43:22 TeX-influenced. 11:45:13 BTW, crazy idea: : ... ." Code is incomplete! " ; IMMEDIATE 11:50:21 Is BETWEEN reserved for something? 11:51:03 BOUNDED ? 11:58:10 I would do "BETWEEN?" 12:48:14 --- quit: Nutssh ("Client exiting") 15:13:05 --- quit: ASau (Read error: 110 (Connection timed out)) 16:39:23 --- join: Sonarman (~matt@adsl-64-160-164-88.dsl.snfc21.pacbell.net) joined #forth 16:39:51 --- join: Sonarman_ (~matt@adsl-64-160-164-88.dsl.snfc21.pacbell.net) joined #forth 16:40:07 --- quit: Sonarman_ (Client Quit) 16:47:55 --- quit: OrngeTide (Read error: 60 (Operation timed out)) 16:55:17 quiet here 16:56:33 Yes. 16:56:58 But I found an old forther on EFnet, she's playing with Forth now for the first time in 20 years.. 17:11:03 and it hasn't changed much :) 17:13:25 Hehe 17:18:03 --- join: blockhead (default@dialin-1007-tnt.nyc.bestweb.net) joined #forth 17:19:00 --- join: proteusguy (~proteusgu@216.27.161.121) joined #forth 17:19:29 --- quit: proteusguy (Read error: 54 (Connection reset by peer)) 17:19:53 --- join: proteusguy (~proteusgu@216.27.161.121) joined #forth 17:24:06 --- join: default_ (default@dialin-869-tnt.nyc.bestweb.net) joined #forth 17:31:00 hi all 17:31:26 hey 17:32:01 tonight i'll try to work on the compiler so that 100 more words are compiled properly :) 17:32:03 --- nick: default_ -> blcokhead 17:32:10 woops 17:43:51 --- quit: blockhead (Read error: 113 (No route to host)) 17:44:14 --- nick: blcokhead -> blockhead 17:46:29 HI ALL 17:48:59 howdy 17:50:18 Robert: hey 17:50:27 Robert: who's the forther you found :) 17:50:37 Er, nevermind. 17:50:44 .. 17:55:47 Robert: why nevermind? 17:56:04 hi chris-xp 17:56:18 slava: Hi slava :) 17:56:38 slava: what would be the best language to write a protable macro assembler in? 17:56:46 chris-xp, forth :) 17:56:52 naah 17:56:56 why not? 17:56:59 forth isn't good for string parsing. 17:57:02 visual basic! 17:57:05 and not very available! 17:57:06 of course its good for parsing 17:57:14 : FOO ... ; IMMEDIATE 17:57:16 slava: now, that statement desired massive face-punching! 17:57:17 there you go :) 17:57:31 chris-xp, my only other suggestion is factor ;) 17:57:33 or C 17:57:43 yeah, i think C or forth is best for this 17:57:44 how is forth not good for string parsing? 17:57:49 C then, I guess. 17:57:58 C string parsing is not stellar either. 17:57:58 Sonarman: well, you wanna t00t0r me? 17:58:16 i'd give forth's text handling the upper edge just by virtue of the outer interpreter 17:58:20 but C i can parse string in well :) 17:58:24 heh 17:58:48 you could write C-like string handling in a few screens of forth code. 17:59:06 well, its not C-like. 17:59:16 I AM SUCH A RETARD 17:59:26 was chasing a bug in the dataflow analysis for ages 17:59:29 i meant what I'm parsing :) 17:59:35 slava: ? 17:59:36 turns out one part did not consume parameters from the 'simulated' stack 17:59:45 arrggh! 17:59:47 arke! 17:59:48 .......................................... 17:59:50 LOL! 17:59:51 haha 18:01:36 I could always go with Brainfuck... 18:01:37 lol 18:01:51 but ... no 18:02:04 why not assembler :) 18:02:07 why are you writing one anyway 18:02:09 slava: J# is Java "backwards compatible"? 18:02:10 nasm exists :) 18:02:15 chris-xp, don't use J# 18:02:20 slava: because its completely, 100% protable 18:02:32 chris-xp, its a pseudo-jdk 1.1 (ie, 5 years old) that targets the .net VM 18:02:33 slava: like as, but better 18:02:42 oh heh 18:02:46 I often use Forth for compilers/assemblers because of the simplicity of parsing. 18:03:16 but ... I don't want to use forth. 18:03:19 :P 18:03:33 sinner. 18:03:44 qFox: stfu n00b 18:03:44 :P 18:03:50 fine fine 18:03:54 i'll go sleep 18:03:55 tsk 18:03:56 chris-xp, why not 18:04:03 qFox: :) sorry. Good night. 18:04:07 np :p 18:04:13 slava: because I need something very available. 18:06:18 chris-xp, here is a hard problem: deducing stack effects of recursive functions that themselves take code quotations as parameters 18:06:28 eg, factor's EACH function 18:06:34 [ 1 2 3 ] [ . ] each 18:06:44 heh 18:06:46 yeah! 18:06:55 1 2 3 ok :) 18:07:07 what does this do? 18:07:10 [ dup cons ] dup cons 18:07:12 ... 18:07:14 oh 18:07:17 erm, lol 18:07:28 [ dup cons dup cons ] 18:07:43 almost 18:07:46 [ [ dup cons ] dup cons ] 18:07:53 now suppose i have this on the stack 18:07:57 and i evaluate CALL 18:08:00 what is left on the stack 18:08:30 [ [ dup cons ] dup cons ] 18:08:32 lol 18:09:41 what about this : hello "hello" see ; hello :-) 18:09:50 --- join: MrReach (~spam@209.181.43.190) joined #forth 18:09:50 --- mode: ChanServ set +o MrReach 18:09:57 hi MrReach 18:10:02 hihi 18:10:04 hi MrReach 18:10:16 slava: erm... what does see do in factor? :) 18:10:23 --- join: Robert_ (~snofs@c-8f5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 18:10:29 chris-xp, same as in forth but its not a parsing word 18:10:41 because if this was forth, it would show the def for ; and then give an error about not knowing about hello 18:10:57 --- quit: Robert (Read error: 104 (Connection reset by peer)) 18:11:17 (Connection reset by beer) 18:15:45 --- quit: qFox ("if at first you dont succeed, quit again") 18:18:37 --- quit: blockhead (No route to host) 18:30:28 --- join: kc5tja (~kc5tja@66-91-231-74.san.rr.com) joined #forth 18:30:42 --- mode: ChanServ set +o kc5tja 18:33:12 --- nick: Robert_ -> Robert 18:33:28 hi kc5tja 18:33:31 hi kc5tja 18:34:03 re 18:36:00 Hi 18:36:04 * kc5tja is going to the store. 18:36:06 Back in a bit. 20:02:55 --- quit: proteusguy (Read error: 60 (Operation timed out)) 20:17:24 --- join: proteusguy (~proteusgu@216.27.161.121) joined #forth 20:23:07 --- quit: proteusguy ("Leaving") 20:41:12 Back. 20:41:24 Back a while ago, actually, but after eating, I fell asleep. 21:00:19 --- join: networm (~networm@L0662P08.dipool.highway.telekom.at) joined #forth 21:00:40 hi. ;) 21:02:53 hi 21:23:14 hi 21:37:29 --- join: ASau (~asau@158.250.48.196) joined #forth 21:39:31 Dobroe utro! 21:40:55 hi ASau 21:42:48 i eliminated about 200 lines of code from my interpreter 21:43:01 :) 21:43:03 Congratulations. 22:06:33 looks like i broke something pretty badly: 22:06:33 ERROR: Stack effect of [ r> r> dup >r swap >r call r> r> while ] ( I -- O O O O O O O O O ) is inconsistent with [ r> drop r> drop ] ( I -- O O O O ), head is ( I -- O O O O r:O r:O ) 22:07:06 i need a test suite 22:07:21 l0l 22:08:11 and yes, the code in those quotations is pretty scary too. 22:13:16 i replaced r> r> dup >r swap >r 22:13:18 with rover r> 22:13:26 where rover is ( r:A r:B -- r:A r:B r:A ) 22:15:47 --- join: chris-cyg (~Chris@wbar8.lax1-4-11-099-104.dsl-verizon.net) joined #forth 22:17:46 --- join: arke (~Chris@wbar8.lax1-4-11-099-104.dsl-verizon.net) joined #forth 22:17:56 hi arke 22:18:47 well, I'm actually chris-cyg... 22:19:10 --- quit: chris-cyg (Read error: 104 (Connection reset by peer)) 22:19:31 --- nick: arke -> chris-cyg 22:42:03 --- quit: ChanServ (Shutting Down) 22:46:45 --- quit: MrReach (kornbluth.freenode.net irc.freenode.net) 22:46:47 --- join: ChanServ (ChanServ@services.) joined #forth 22:46:47 --- mode: irc.freenode.net set +o ChanServ 22:47:43 quick bash question... 22:47:51 --- join: MrReach (~spam@209.181.43.190) joined #forth 22:47:51 --- mode: irc.freenode.net set +o MrReach 22:48:17 if blah returns 0 when successful, and I want foo to be executed if it is, should I do blah && foo or blah || foo? 22:49:21 blah && foo 22:49:30 ok thanks 22:58:20 --- quit: Sonarman (Read error: 110 (Connection timed out)) 23:08:56 Sorry, but that won't work. 23:08:59 blah || foo is correct. 23:09:05 && and || are short-circuit operations. 23:10:23 So if && sees that blah returns 0, and since no matter WHAT foo does it will return a zero anyway, foo won't even be executed. 23:10:43 So what you want is ||, because this way, if blah returns 1, then foo doesn't execute (since || already knows ahead of time the result will be 1). 23:11:01 However, that being said, THAT KIND OF C CODE IS DISASTEROUSLY HARD TO MAINTAIN and is the SCORN OF THE EARTH. 23:11:15 It's much easier in the long run to just plain use nested IF statements or something. 23:19:12 I thought he was talking about bash 23:19:13 not c 23:19:33 I could have been mistaken. 23:26:45 kc5tja, i have it burned in my mind that a && b == if(a) { b; } else false; 23:26:53 and also for || 23:28:10 408 out of 850 words compile but there is a new bug since selecting 'new game' enters the debugger straight away :( 23:32:52 Nope. 23:33:00 Oh, sorry, yeah. 23:33:09 I thought that read a || b above. 23:33:24 If, and only if, a is true, then b executes. 23:33:37 --- quit: Herkamire ("bedtime") 23:35:51 and it gets really confusing when bash treats 0 as true :P 23:36:26 Yeah. 23:36:29 Don't mind me. 23:36:32 * kc5tja is getting tired. 23:36:46 Spent four hours hacking on my customer's code, adn I'm still in the "C" mindset thusly. 23:40:17 i like C. I finally understand the , operator now since I started this forth VM. x = (VM->pop (), VM->x); 23:41:42 I like C well enough, but I'd *much* rather be coding this project in Forth. 23:46:27 which Forth would i use to get optimized binaries out of it? 23:46:34 something like "gcc" is for C 23:46:50 Probably BigForth for Linux. 23:47:23 Also, most modern commercial Forth systems are highly optimizing nowadays too. 23:48:12 ah, yes, i forgot, it should be free and for linux :) i'll look at BigForth 23:49:28 hm, doesn't seem to be in debian 23:50:01 I'm not aware of any packages for it for any distro. 23:59:59 --- log: ended forth/04.02.27