00:00:00 --- log: started forth/05.03.17 00:46:00 --- join: I4404__ (~mark4@216-110-82-203.gen.twtelecom.net) joined #forth 01:01:33 --- quit: I440r_ (Read error: 110 (Connection timed out)) 02:28:57 --- quit: Herkamire ("off to bed") 02:44:10 --- quit: docl (Read error: 104 (Connection reset by peer)) 03:06:19 --- join: Freejack (~nicad@c-24-11-30-248.client.comcast.net) joined #forth 03:24:26 --- quit: Freejack ("Leaving") 04:05:13 --- join: Topaz (~top@cerberus.saywell.net) joined #forth 04:29:18 --- quit: Topaz (Read error: 113 (No route to host)) 05:23:03 --- join: tathi (~josh@pcp01375108pcs.milfrd01.pa.comcast.net) joined #forth 05:51:13 damn, I love PPC assembly language sometimes. 05:52:01 instructions to insert or extract a generic bitfield are just cool. :) 05:58:06 --- quit: aum () 08:47:45 --- join: Topaz (~top@cerberus.saywell.net) joined #forth 09:07:19 --- join: Serg[GPRS] (~z@193.201.231.126) joined #forth 10:44:49 --- quit: ASau (Read error: 104 (Connection reset by peer)) 10:47:45 --- quit: Serg[GPRS] () 11:51:37 --- join: djo (~djo@djo.rezel.enst.fr) joined #forth 11:52:18 hello 11:52:55 hi djo 11:53:58 just a question 11:54:36 how does forth treat boolean values 11:54:58 I mean in an exmple like "5 4 <" 11:55:31 in the spec it's said that the stack contains a flag 11:55:43 is it and integer flag ? 11:55:46 yes. 11:55:56 0 is false 11:56:03 -1 (all bits set) is true. 11:56:28 though anything other than 0 will work for true. 11:57:35 think you 11:57:52 sure. 12:25:15 --- join: zol1 (~l@ppp-82-135-6-218.mnet-online.de) joined #forth 12:25:29 g'day 12:29:24 Hey. 13:27:42 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 13:27:42 --- mode: ChanServ set +o Herkamire 13:48:57 teh hies 13:58:10 --- join: aum (84d16c6c8f@60-234-138-239.bitstream.orcon.net.nz) joined #forth 14:15:38 the hives? 14:25:39 hi 14:54:59 --- quit: Topaz (Remote closed the connection) 14:56:02 --- join: Topaz (~top@cerberus.saywell.net) joined #forth 15:11:08 is forth case sensitive ? 15:11:39 in words names 15:11:41 sometimes 15:11:53 most of the time it is, i think, but I'm not sure :) 15:12:03 easiest way to test is type 15:12:08 : FOO ; foo 15:12:13 and see if it gives an error 15:12:13 :) 15:12:26 Hopefully it isn't, and if it is, hopefully it can be switched off. Case-sensitivity is allowed by the Standard, but there's talk of voting it out in an addendum. 15:29:47 --- quit: I4404__ ("Leaving") 15:32:16 --- quit: Topaz (Remote closed the connection) 15:32:37 tathi, what's an easy way to branch somewhere if a register contains the value 3? 15:35:18 oh man, you have to manually clear the condition register? 16:46:43 --- join: ecraven (nex@A-036.AHL.Uni-Linz.AC.AT) joined #forth 16:46:48 hey :) 16:48:42 is there anything newer than Koopman - Stack Computers, that i can read about implementation of stack machines, available freely on the internet? 16:52:59 like...optimizing forth compilers stuff? 16:53:01 I think Anton Ertl has some papers. 16:53:09 or actual forth processors, or what? 16:53:52 Ertl called his optimizing framework RAFTS I think. 16:54:09 tathi: yes, actual forth processors would be interesting as well :) 16:54:21 http://www.complang.tuwien.ac.at/projects/rafts.html 16:54:30 wee, tu wien?? nice! 16:54:51 some papers at the bottom, been a long time though, don't remember how good they are. 16:56:03 http://www.forthfreak.net/index.cgi?ForthCPUs (ForthFreak wiki) 16:56:03 thanks for the pointer :) 16:56:28 how well designed is the jvm, by the way? 16:58:24 In what regard? 16:58:56 the jvm is not a true stack machine 17:00:37 i'm looking into a stack machine VM for Scheme.. and it seems Forth is the starting point for learning more about stack machines :) 17:01:16 I'd say it is, certainly from a practical standpoint. 17:02:30 ecraven, you might want to look at my factor language, its a mix of forth and lisp, stack based 17:04:15 slava: where do i find it? 17:04:27 ecraven, factor.sourceforge.net. we have an irc channel #concatenative 17:05:48 slava: wow, that looks interesting.. how many stacks do you use? 17:06:01 ecraven, data stack and return stack are the primary ones, just like forth 17:06:01 i've been thinking about continuations when using multiple stacks.. 17:06:14 but we also have a catch stack for exception handling, and a name stack for dynamic variables 17:06:14 how do continuations interact with that? you save all stacks? 17:06:17 yes 17:06:52 ecraven, i have to go now, sorry. good luck with your scheme implementation 17:07:02 thanks, i'll hang around :) 17:07:09 i have to read a lot more :) 17:16:22 --- join: hyrax (~chatzilla@64.219.100.33) joined #forth 17:20:25 --- quit: tathi ("ta") 17:31:29 what are the advantages of having a separate return address stack compared to just putting return addresses onto the parameter stack? 17:32:02 ecraven: the stack is the forth way of passing data. 17:32:44 ecraven: if you have a separate stack for call addresses, you eliminate the need to juggle that around. And also, it gives you an extra place to temporarily store stuff. 17:32:52 And its also much MUCH cleaner and faster to implement 17:36:46 hm.. so much to learn :) i'll continue reading this book and be back with questions :) but first some sleep, it's getting late.. thanks for all the help 18:00:49 --- quit: ecraven ("good night :)") 18:30:29 --- join: I440r_ (~mark4@216-110-82-203.gen.twtelecom.net) joined #forth 18:30:46 --- quit: aum () 18:33:48 goodnight 18:40:04 --- quit: I440r_ ("Leaving") 19:33:11 --- quit: I440r ("Leaving") 19:40:11 --- join: I440r (mark4@rrcs-24-242-160-169.sw.biz.rr.com) joined #forth 20:02:32 --- quit: Herkamire (Read error: 60 (Operation timed out)) 20:46:47 --- join: aum (~aum@60-234-138-239.bitstream.orcon.net.nz) joined #forth 20:51:26 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 20:51:26 --- mode: ChanServ set +o Herkamire 21:52:20 --- quit: I440r ("Leaving") 21:54:29 --- join: I440r (mark4@rrcs-24-242-160-169.sw.biz.rr.com) joined #forth 22:14:23 --- quit: aum () 22:16:55 --- quit: zol1 (Read error: 110 (Connection timed out)) 23:59:59 --- log: ended forth/05.03.17