00:00:00 --- log: started forth/07.02.07 00:18:20 --- quit: arke (Read error: 110 (Connection timed out)) 00:46:01 --- join: ecraven (n=nex@eutyche.swe.uni-linz.ac.at) joined #forth 01:01:44 groetjes ASau 01:06:42 Guten Tag. 01:16:11 hmm? is today the big greet in german day? 01:16:38 :) 01:17:04 Have you ever heard about Ilja Il'f and Evgenij Petrov? 01:17:28 no I haven't 01:18:29 http://en.wikipedia.org/wiki/Ilf_and_Petrov 01:18:54 There's a character in "12 Chairs", 01:20:50 Kisa Vorobjaninov 01:21:28 ok 01:21:30 he used to greet himself with various greetings depending 01:21:30 on his mood, 01:21:48 When in bad one he greeted himself with "Guten Morgen." 01:22:11 :) 01:22:35 well, that's a little sidekick to those who speak german 01:22:57 Even more. 01:23:13 In good mood he greeted himself with "bon jour". 01:23:43 :) 01:23:58 --- join: Cheery (n=Cheery@a81-197-54-146.elisa-laajakaista.fi) joined #forth 01:23:59 => the good: france, the bad: german? 01:24:05 Right. 01:25:07 It is hard to explain in dozen words, you have to understand the background. 01:28:24 well, WW1 01:28:25 I mean you should understand this "german vs. french" issue in russian framework. 01:28:44 I does not involve WWs. 01:29:46 ok, then something before it? 01:30:49 It goes from times of Anna I and Ekaterina II. 01:31:12 ~1750's and 1770's resp. 01:32:05 aha. 01:47:49 --- quit: arke_ (Read error: 110 (Connection timed out)) 02:11:21 --- quit: azekeprofit (Read error: 104 (Connection reset by peer)) 02:54:21 --- join: mark4_ (n=mark4@70.102.202.162) joined #forth 02:55:57 --- quit: I440r (Read error: 104 (Connection reset by peer)) 04:00:04 how does it come that there is the lisp convention to write functions-extra-long-with-every-little-detail-what-the-function-does-into-its-name? 04:02:37 so you can understand what it does just be reading its name :) 04:02:55 --- join: vatic (n=chatzill@ool-45740b1c.dyn.optonline.net) joined #forth 04:03:49 --- quit: vatic (Client Quit) 04:06:02 thanks, really that's not the kind of information I was asking for. 04:07:47 I meant with my question to get answers when this style of code writing first appeared in lisp. 04:59:40 virl: from this page http://www-formal.stanford.edu/jmc/ ... 05:00:09 I found this http://www-formal.stanford.edu/jmc/lisp20th.html 05:00:24 and if there is an answer it may be in that document 05:10:46 well, it seems that it's not in this document. whatever 05:11:23 Ya, I just read it too, sorry. :( 05:11:52 I-don't-know-where-the-hyphenated-construction-come-from. 05:15:52 I only wondered, because I'm too one of those people who like to give it's functions a good name, but that hyphenated construction is for me a little bit too extreme. 05:28:29 --- join: arke (n=chris@x178.vpn.hrz.tu-darmstadt.de) joined #forth 05:28:29 --- mode: ChanServ set +o arke 05:33:30 --- join: azekeprofit (i=azekePro@82.200.252.218) joined #forth 05:47:23 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 06:23:23 --- quit: arke (Read error: 145 (Connection timed out)) 06:40:08 wah, boring.. 06:40:24 let's see what happens on comp.lang.forth 06:59:57 --- quit: Quartus_ (Read error: 60 (Operation timed out)) 07:10:41 --- join: arke (n=chris@pD9E075B5.dip.t-dialin.net) joined #forth 07:10:41 --- mode: ChanServ set +o arke 07:24:39 --- quit: mark4_ (Read error: 110 (Connection timed out)) 07:25:43 --- join: arke_ (n=chris@pD9E075B5.dip.t-dialin.net) joined #forth 07:25:44 --- quit: arke (Read error: 54 (Connection reset by peer)) 07:42:28 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 07:42:28 --- mode: ChanServ set +o tathi 08:18:58 --- join: Quartus_ (n=Quartus_@209.167.5.1) joined #forth 08:18:58 --- mode: ChanServ set +o Quartus_ 08:26:47 --- quit: grub_booter (Read error: 110 (Connection timed out)) 08:28:13 --- join: grub_booter (n=charlie@d54C37C64.access.telenet.be) joined #forth 09:16:34 --- quit: ecraven ("bbl") 09:26:57 --- join: Zarutian_ (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 09:26:58 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 09:29:55 --- nick: Zarutian_ -> Zarutian 09:34:23 --- join: Crest (n=crest@p54897BEC.dip.t-dialin.net) joined #forth 10:19:39 --- join: mark4 (n=mark4@70.102.202.162) joined #forth 10:21:28 --- quit: Quartus_ (Read error: 60 (Operation timed out)) 10:51:37 --- join: Quartus_ (n=Quartus_@209.167.5.1) joined #forth 10:51:37 --- mode: ChanServ set +o Quartus_ 11:46:56 --- join: Snoopy17 (i=snoopy_1@dslb-084-058-114-207.pools.arcor-ip.net) joined #forth 11:47:33 --- quit: Snoopy42 (Nick collision from services.) 11:47:41 --- nick: Snoopy17 -> Snoopy42 12:07:23 --- join: edrx (n=Eduardo@201.5.12.213) joined #forth 12:44:18 --- quit: edrx (Read error: 148 (No route to host)) 12:56:59 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 13:30:13 --- quit: Quartus_ (Read error: 104 (Connection reset by peer)) 13:31:12 --- quit: timlarson_ ("Leaving") 13:57:18 --- join: mark4_ (n=mark4@70.102.202.162) joined #forth 13:58:55 --- quit: mark4 (Read error: 104 (Connection reset by peer)) 13:59:14 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/") 14:04:15 --- quit: grub_booter (zelazny.freenode.net irc.freenode.net) 14:04:26 --- join: grub_booter (n=charlie@d54C37C64.access.telenet.be) joined #forth 14:21:40 --- join: imaginator (n=George@georgeps.dsl.xmission.com) joined #forth 14:26:52 --- join: Quartus_ (n=Quartus_@209.167.5.2) joined #forth 14:26:52 --- mode: ChanServ set +o Quartus_ 14:33:24 what forth today? :) 14:38:21 hmm, forth needs a binding generator. 14:42:35 C is fine for this, when almost everything is written in C 14:43:16 I'm building a widget tree in ficl, so I guess ficl is the forth of today. :) 14:44:01 sure? ficl is ANS compliant, iirc. 14:44:44 or what does it make to be a today forth? 14:46:54 what does it make? 14:47:38 I meant which features does it offer? 14:47:59 oh, well I'm constructing trees for each client in my window system. 14:48:08 actually each client window 14:48:48 so .top might be the application's main window, and .top.exit and .top.say-hello might be buttons. 14:49:54 aha, and what are your trees based on? 14:50:11 because the widgets are going to be destroyed and created at random (random names too) (depending on the app) I decided I couldn't use create, so I'm constructing it with allocate (for the most part). 14:50:22 or is .top.exit simply : .top.exit? 14:51:42 this is the current syntax I'm aiming for, in this module: S" .top" some-address-for-a-window-struct tree mytree-variable tree-insert 14:52:47 So it's not using the dictionary directly for .top and .top.exit 14:53:39 then I'll eventually have tree-find (if I can get this all working) that works like this: S" .top" mytree-variable tree-find 14:54:08 I assume that uses a lot of code, for comparing the string 14:54:32 I'm using a string module I wrote too 14:54:52 I can show you, if you're interested. It has tests. I'm not sure how useful it would be to others, but it's useful for me. 15:01:46 here's my string code http://rafb.net/p/ByGzmC73.html it uses the jhlocals.f feature builtin to Ficl, so it may not be entirely portable :) 15:01:59 --- join: Snoopy42 (i=snoopy_1@dslb-084-058-132-158.pools.arcor-ip.net) joined #forth 15:20:24 --- join: Quartus (n=trailer@CPE0001023f6e4f-CM013349902843.cpe.net.cable.rogers.com) joined #forth 15:26:25 --- quit: Crest ("This computer has gone to sleep") 15:41:04 --- quit: mark4_ ("Leaving") 18:24:32 --- quit: crc (Remote closed the connection) 18:34:20 --- join: crc (n=crc@pool-151-197-2-179.phil.east.verizon.net) joined #forth 18:38:04 --- join: nighty (n=nighty@sushi.rural-networks.com) joined #forth 19:03:30 --- quit: madwork (Read error: 110 (Connection timed out)) 19:07:39 --- quit: nighty (Client Quit) 19:50:55 --- quit: tathi ("'night") 20:08:46 --- quit: madgarden (Read error: 131 (Connection reset by peer)) 20:10:26 --- quit: segher (Read error: 60 (Operation timed out)) 20:12:19 --- join: segher (n=segher@dslb-084-056-129-145.pools.arcor-ip.net) joined #forth 20:13:24 --- join: slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 20:13:24 --- mode: ChanServ set +o slava 21:15:20 --- quit: imaginator (".") 21:51:13 JasonWoof: ping 21:51:27 "It is important that the decrement and update happen atomically (for example, with stwu, stwux, stdu, or stdux) so that the stack pointer and back-link are in a consistent state. Otherwise asynchronous signals or interrupts could corrupt the stack." 21:51:37 it appears that OS X requires the backlink to always be there :-) 21:52:28 ok 21:52:36 so if you want to use your own stack it can't be r1 21:52:51 right 21:54:10 I wouldn't use r1 unless I was going to be compatible with the other stuff that uses r1 22:17:42 --- quit: JasonWoof ("off to bed") 22:22:54 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 22:23:08 --- join: Zarutian (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 22:23:57 moo 23:20:38 --- join: edrx (n=Eduardo@201.5.12.80) joined #forth 23:41:19 --- quit: neceve (Remote closed the connection) 23:59:36 --- join: arke__ (n=chris@pD9E0571F.dip.t-dialin.net) joined #forth 23:59:59 --- log: ended forth/07.02.07