00:00:00 --- log: started forth/10.12.04 00:19:18 --- join: zzo38 (~zzo38@h24-207-49-17.dlt.dccnet.com) joined #forth 00:20:45 I tried making a word overriding by using DOES-CODE! but that doesn't work because the compiled code to call such a word is different. 00:21:11 First time I've heard about pcc 00:22:28 Can you tell me how to correct this problem, please? 00:23:35 What forth are you using? 00:24:03 (I'm fairly new to forth, so not sure if I can help) 00:24:52 Gforth 00:35:13 If you are new to Forth, tell me if you have a question, too. I might or might not know the answer of your question. 00:59:32 --- quit: zzo38 (Remote host closed the connection) 02:07:32 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 02:37:05 --- join: kar8nga (~kar8nga@m-47.vc-graz.ac.at) joined #forth 02:51:35 --- quit: gogonkt (Ping timeout: 265 seconds) 02:53:04 --- join: gogonkt (~info@113.105.207.177) joined #forth 03:25:05 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 03:36:22 --- quit: MayDaniel () 04:08:23 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 04:16:33 --- quit: MayDaniel (Read error: Connection reset by peer) 04:57:10 O_o 05:19:12 What? 05:19:27 Sounds like another "september." 05:58:12 --- quit: mathrick (Remote host closed the connection) 05:58:18 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 06:21:45 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 06:31:27 ASau: "september" ? 06:31:55 When does academic year start there? 06:32:41 Lookup "eternal september" in jargon file. 06:33:55 ASau: I was puzzled by what zzo38 was asking. 06:34:12 I don't understand it in full either. 06:34:56 I think he wants to get all his words using DOES-CODE! recompiled. 06:34:59 * schmrkc shrugs. 06:35:11 I don't even know what it does. 06:35:17 me neither. 06:35:26 This is something gforth-specific. 06:35:38 dodoes: over ! cell+ ! ; 06:35:39 "carnal knowledge" :D 06:35:51 well doedoes was brilliant. 06:36:12 see dodoes: => : dodoes: 140299348050976 @ ; 06:37:04 All this area is shaky ground. 06:38:28 "does>" is controversial Forth merit. 06:39:17 give 'em enough rope, etc. 06:40:35 It still isn't clear, if having no "does>" really doesn't bring any improvement. 06:44:12 oh hush. Have you not been informed that it brings functionality to forth that makes forth shine out through the masses, and with it you can do things nothing else will ever let you do? 06:44:40 :) 06:45:01 Yeah. 06:45:36 This religious zeal is sometimes amusing. 06:45:56 Except when it becomes extremely annoying. 06:46:07 Now that you have me thinking about it I don't think that I use does> all that extremely much. 06:46:10 * schmrkc nods nods. 06:46:17 lisp has it worse it seems :) 06:47:09 At least they don't write standard proposals on bi-monthly basis. 06:47:45 Plus, there're much more educated people in the community, 06:48:12 Yeah. Usually it's just people pretty new to lisp who are religious nutters. 06:48:14 many of them didn't waste their time in university. 06:48:46 Just the other day someone accused me for trolling because I disagreed with the FACT that "once you have learnt lisp then working in anything else will be a painful experience" 06:49:15 At least, there's no problem in finding people who 06:49:15 understand what is methodologically correct experiment. 06:50:11 oh well it's all good. 06:50:23 Forth community is dominated by hugh aguilars. 06:50:46 I didn't even know there was a forth community. 06:50:58 news:comp.lang.forth 06:51:04 aha 06:51:24 my ISP figured providing a newsserver was not so important so I haven't bothered with usenet for the last 8 years :) 06:51:31 for good and bad. 06:53:47 My impression is that community consists almost completely of old farts, 06:54:11 with only some of them suddenly realised how far Forth is 06:54:11 lagging behind the rest of the world. 06:54:34 aha. That is my impression too. 06:54:53 But their attempts to catch up look more like updating from state of art of 70s to state of art of 80s. 06:55:43 I can't really imagining using forth for anything but my "embedded" projects. 06:55:51 imagine 06:55:58 which I guess says a lot about forth. 06:56:28 I can imagine more, but it still requires significant modifications to Forth. 06:56:37 Right, that's what I meant. 06:56:54 One if them is name spaces or other modularity features. 06:57:10 I have a hobby of writing backgammon software. forth is one I have avoided for doing that. 06:57:18 Right now I'm tinkering into FICL and pForth. 06:57:33 With both resisting substantial changes. 06:58:13 I'm thinking about breaking performance microoptimisations in FICL to ease major changes. 06:58:25 What's the argument against change? I'm thinking people are going with 'but it has worked up til now, why change it if its not broken?' which doesn't work if its all OldFarts. 06:58:35 For pForth? 06:58:38 sure. 06:58:43 Backward compatibility. 06:58:47 ouch. 06:58:55 It is hard to explain that you _have_ to break it. 06:59:02 if you want to achieve any good. 06:59:04 There's a time for that, yea. 06:59:11 and ... well.. 06:59:26 porting all pforth software to work with the change.. can't be that much software :) 06:59:31 Any program that depends on dictionary layout isn't portable anyway. 06:59:35 And never has been. 06:59:52 depending on dictionary layout?? 06:59:57 Yes. 07:00:13 huh. 07:00:35 It uses that stupid "optimisation" hack from 80s, 07:00:54 when it was usual to have negative displacements in data structures. 07:00:58 the world of forth makes me sad. 07:01:09 In microcomputer field. 07:01:23 nice. just 30 years out of date then ;) 07:02:08 It is hard to tell exactly. 07:02:24 I've seen somewhere on NetBSD list that 07:02:44 "libraries that print error messages to stderr are so 70s" 07:02:51 O_o 07:02:57 where else should they print e 07:02:59 'em? 07:03:10 may slightly differ from original. 07:03:27 This was from Christos Zoulas, if you know who he is. :) 07:03:32 Not an idea. 07:03:40 One of NetBSD founders. 07:03:47 I should reinstall netbsd on my laptop I feel. It was a nice environment. 07:04:14 I hade to install ubuntu over it for Lisa's hospital visit for a while. heff. 07:04:17 I thought that libraries that dump error messages to stderr are "so 80s." 07:04:28 Where should error messages go? 07:04:37 Nowhere. 07:05:00 huh. how do you find 'em then? 07:05:05 If you want human readable errors, implement strerror-like interface. 07:05:50 ya but you need to put that error somewhere, no? 07:06:00 That's library. 07:06:18 oh! 07:06:21 library 07:06:25 right now I'm following. 07:06:25 If you receive error status code from library function, you can do with it everything what you want. 07:06:32 yes, I agree 100% there. 07:07:00 Just in case you don't follow, this is demonstration that "30 years" may be too optimistic. 07:07:33 That's something I like with erlang. the caller of things is responsible. 07:08:16 * schmrkc needs more coffee. 07:08:19 This is general understanding who is responsible. 07:08:23 I guess forth will keep dying. 07:08:34 It doesn't depend on programming language. 07:08:41 true true. 07:08:49 Sometimes I think that I should try to port Poplog. 07:09:05 Or ask Sloman to do that. 07:09:10 never used no poplog. 07:09:32 POP is said to be one of Forth predecessors. 07:10:50 hmmm.. 07:11:37 comp.lang.pop seems a bit dead. 07:11:40 BTW, I have managed to coerce pForth to run my testing & coverage code. 07:11:54 sounds great. What are you doing with pforth? 07:12:05 The result is that coverage dropped from 0,9 to 0,5. 07:12:46 oops. 07:12:47 Some PIM, various data conversion, primitive calculations. 07:12:56 Yeah. 07:13:02 This shows how portable Forth code is. 07:13:38 striving for portability, eh. 07:14:04 I guess that only holds for the vm. 07:14:09 More like freedom. 07:14:23 * schmrkc looks around the channel. 07:14:24 I'm sick of GPL dictatorship. 07:14:29 but it's not GPL. How can it be freedom!? 07:14:30 ;) 07:15:09 I don't see there's "free" in "gpl". 07:15:16 Me neither. 07:15:24 or some odd definition of what freedom means. 07:15:33 Its conditions become more and more obscure each year. 07:15:43 can't wait for v4. 07:16:32 Another joke is FSF selling all rights to Oracle. 07:16:39 What!? 07:16:57 Note that FSF _requires_ to transfer all rights on gnu code to them. 07:17:44 Have you seen what happened to Sleepycat and MySQL code? 07:18:07 See I don't mind the FSF and GPL so much. Just as long as I don't have to use it. What I do mind is how certain GPL advocates go on endless rants about how BSD-license is the spawn of the devil, etc. 07:18:12 like they own the word "free" 07:18:20 nope. 07:18:55 Yes, this is what pisses me off. 07:19:16 and the bizarre ideas about freedom, but that I can live with. 07:19:19 oh well. 07:19:28 They redefine meaning of "free" and talk as if it is the only meaning from now on. 07:19:44 * schmrkc nodsnods. 07:20:06 with free being "you can do this here. but only if you do this. and you can't do that." 07:21:38 The problem isn't that there're conditions. 07:22:08 It's that these conditions are obscure and sometimes not even sensible. 07:22:17 I'm a bit amused by how certain people like to claim other things are "non-free" just because they're not GPL. 07:23:42 Alright. 07:24:09 If you want some help with pForth or FICL, you know what you can try :) 07:24:14 * schmrkc needs to get some coffee and get something done. 07:24:17 huff. 07:24:19 I'm back to coding tasks. 07:24:30 maybe I'll try porting it to AROS if I ever get the sdk built. 07:24:47 Do you run that old stuff? 07:25:09 I installed it on my laptop just last week. 07:25:15 instead of ubuntu. 07:25:23 AROS??? 07:25:27 AROS 07:25:42 Wasn't it 68k Amiga stuff? 07:26:08 (url?) 07:26:09 well it's to amigaos like reactos to windows I guess. 07:26:18 and latest amigaos is ppc 07:26:24 Ah. 07:26:32 (because the latest amigas were ppc) 07:26:36 So it's still in 68k tradition. 07:26:40 http://aros.sourceforge.net/ 07:26:42 right. 07:26:44 No, I'm in x86 world. 07:26:47 cept AROS then which runs on x86 07:26:50 and x86-64 07:27:41 Last time I considered buying anything non-x86, I was impressed by price. 07:27:48 And this impression was bad. 07:27:50 * schmrkc nods. 07:28:00 I have been looking at buying an ARM-based laptop and/or desktop. 07:28:13 but then the EEEPc rocks the arm lappy in every way. 07:28:18 including battery time. so meh. 07:28:27 When they really make their RISCs competitive, I'll reconsider it. 07:28:30 the new amiga looks somewhat interesting. 07:28:32 ya 07:28:51 I'm consent that it may operate with less peformance, 07:29:02 but either not that much or not for that price. 07:29:13 I'd want more battery time from a lappy. That's my main thing there. and not at much higher the price. 07:30:17 I have looked at sparc server which costs here 2 or 3 times more than better amd64 server. 07:30:26 ya 07:30:32 opteron is killing the sparc it seems. 07:31:23 http://en.wikipedia.org/wiki/AmigaOne_X1000 is supposed to be coming "late 2010" 07:31:24 I have looked at mITX sized single-board computer with MIPS or ARM which costs 1,5x more than better performant i386 or amd64 board. 07:31:30 ya 07:32:29 Sorry, guys. 07:32:38 yeah time to get shit done. 07:32:53 At these costs, I'll buy something conventional. 08:12:32 --- quit: MayDaniel (Ping timeout: 264 seconds) 08:39:33 --- quit: kar8nga (Remote host closed the connection) 09:16:36 --- quit: ASau (Remote host closed the connection) 09:19:36 --- join: ASau (~user@95-28-62-161.broadband.corbina.ru) joined #forth 09:21:48 --- join: Rods_Tiger (~ian_tinda@host86-174-216-182.range86-174.btcentralplus.com) joined #forth 09:30:17 --- quit: Rods_Tiger (Ping timeout: 245 seconds) 09:38:36 --- join: Rods_Tiger (~ian_tinda@host86-174-216-182.range86-174.btcentralplus.com) joined #forth 09:57:12 --- join: ASau` (~user@95-26-92-102.broadband.corbina.ru) joined #forth 09:59:01 --- quit: ASau (Remote host closed the connection) 10:00:13 --- quit: ASau` (Read error: Connection reset by peer) 10:02:45 --- join: ASau` (~user@95-26-92-249.broadband.corbina.ru) joined #forth 10:12:11 --- join: ASau`` (~user@95-27-197-147.broadband.corbina.ru) joined #forth 10:16:07 --- quit: ASau` (Ping timeout: 264 seconds) 10:20:06 --- nick: ASau`` -> ASau 11:28:20 --- join: impomatic (~chatzilla@87.115.229.189) joined #forth 12:58:10 --- join: PoppaVic (~pops@unaffiliated/poppavic) joined #forth 13:02:29 gcc seems to be smart enough, I'm ready to kill this microoptimisation. 13:19:37 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #forth 13:19:56 --- quit: roarde (Client Quit) 14:03:44 --- quit: qFox (Read error: Connection reset by peer) 14:08:27 d/part 14:08:30 --- part: impomatic left #forth 14:09:45 --- join: kar8nga (~kar8nga@j-185.vc-graz.ac.at) joined #forth 14:54:34 hmm i4 no-mo, eh? 15:06:35 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #forth 15:07:23 --- part: roarde left #forth 15:10:04 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #forth 15:19:04 * ASau is profiling pForth... 15:19:14 ahh 15:19:27 pforth is.. interesting 15:19:38 Except when it isn't. 15:19:49 well, the author is happy 15:20:06 The author doesn't seem to use it. 15:20:31 --- quit: kar8nga (Remote host closed the connection) 15:22:31 the author supposedly uses it for assorted jobs/products There's another forth similarly used.. Forgot the name. 15:23:15 I haven't heard from him of any. 15:24:43 I was gonna' pester i4* tonight.. Now I've got a second machine running, I could ppc test for him on osX ;-) 15:24:56 What is "i4"? 15:25:14 check the access list i400r and his isforth, iirc 15:25:18 Ah. 15:25:49 I'm not interested in completely non-portable software. 15:26:09 Nor in "portable" in Forth farts' understanding. 15:26:23 huh? 15:26:49 This is equivalent to "pigs can fly" kind of assertions. 15:27:14 umm.. Fine. 15:27:21 * PoppaVic boggles 15:32:18 PoppaVic in #Forth!?! 15:32:24 Isn't he the ##C guy? 15:33:27 Is it useful to read ##c at all? 15:36:17 not really 15:36:26 Deformative: I am That C Guy ;-) 15:36:53 otoh, I was That Forth Guy before C ;-) 15:37:55 Interesting. 15:39:01 ..so is trying to implement a bytecode/pcode engine in C that works like forth ;-) 15:39:45 Good luck repeating pForth and FICL. :) 15:40:02 yeah 15:40:22 I started out ticked at pforth. 15:41:53 time seconds seconds calls s/call s/call name 15:41:53 9.96 11.04 1.81 101695345 0.00 0.00 memcpy (upstream version) 15:41:53 8.32 10.92 1.42 102512777 0.00 0.00 memcpy (my version) 15:41:58 My version copies less :p 15:42:30 overjoyed 15:44:00 Most time is taken by inner interpreter. 15:45:57 and it's hard to tell if it's good or bad. 15:46:19 Because it performs all stack shuffling, arithmetics, and so on. 15:46:34 so? 15:48:26 I think it just sucks. 15:48:51 that's nice 16:11:07 --- quit: Rods_Tiger (Remote host closed the connection) 17:05:21 --- quit: ASau (Remote host closed the connection) 17:07:07 --- join: ASau (~user@95-27-197-147.broadband.corbina.ru) joined #forth 20:23:23 --- quit: probonono (Quit: Arrgh.. box crashing again!) 21:08:22 --- join: probonono (~User@unaffiliated/probonono) joined #forth 22:19:05 --- quit: gogonkt (Quit: leaving) 22:19:26 --- join: gogonkt (~info@113.105.207.177) joined #forth 23:20:41 --- quit: roarde (Quit: Leaving.) 23:59:29 Woot, there was GPL talk earlier 23:59:59 --- log: ended forth/10.12.04