00:00:00 --- log: started forth/05.03.14 00:09:05 --- quit: Herkamire ("off to bed") 01:42:19 --- join: aum (35b4ff188e@60-234-138-239.bitstream.orcon.net.nz) joined #forth 04:45:26 --- quit: saon ("Lost terminal") 05:11:43 --- quit: aum () 05:24:28 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth 05:55:09 --- join: segher (~segher@blueice3n1.de.ibm.com) joined #forth 06:30:08 --- join: tathi (~josh@pcp01375108pcs.milfrd01.pa.comcast.net) joined #forth 06:39:24 --- quit: tathi ("leaving") 07:43:56 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 07:43:56 --- mode: ChanServ set +o Herkamire 07:45:02 --- join: tathi (~josh@pcp01375108pcs.milfrd01.pa.comcast.net) joined #forth 07:56:50 --- join: slava (~slava@CPE00096ba44261-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 09:53:58 --- join: Serg[GPRS] (~z@193.201.231.126) joined #forth 10:29:29 --- join: serg_ghost (~z@193.201.231.126) joined #forth 10:29:50 hi ! 10:30:06 hi ! 10:30:28 i still not started writing my novel ;)) 10:31:55 * serg_ghost unloads my new camera after test-drive 10:51:50 --- quit: Serg[GPRS] (Read error: 110 (Connection timed out)) 11:17:00 who is the channel owner ? 11:17:45 i wish the logbot to mangle emails =8{Z} 11:24:01 --- join: Topaz (~top@cerberus.saywell.net) joined #forth 11:25:13 Hey Topaz. 11:32:10 --- quit: serg_ghost () 11:32:28 heya 11:35:33 Get that cross-assembler working? 11:42:28 yeah 11:42:44 currently waiting on me fixing WORD (or replacing, rather) to accept delimitation other than spaces 11:42:54 (like newlines) 11:42:57 my code is currently rather unreadable 11:58:39 --- quit: segher ("Leaving") 12:03:13 --- join: docl (~docl@dpcbw099161.direcpc.com) joined #forth 12:17:01 Why do you need to parse across line-endings? 12:17:15 so i can have multi-line word definitions 12:17:28 i dunno if that's bad practice, but it makes things a lot more readable 12:17:43 You can have multi-line word definitions in a system with only REFILL and WORD. 12:17:57 hmm, REFILL? 12:18:29 Yes, usually QUIT calls something often called INTERPRET; that's a loop that REFILLs the input buffer, and then loops over it with WORD (or equivalent). 12:19:21 The only time you'd need to parse across an EOL would be for real oddities like 12:19:22 : 12:19:25 name-of-word 12:19:31 which would be hideously bad form anyway. 12:20:10 i haven't found a need to parse across line boundaries 12:20:17 Nor have I. 12:20:26 i'm defining my own colon compiler 12:20:33 Right. 12:20:38 which currently does BL WORD FIND repeatedly 12:20:50 So when it runs out of text to parse, REFILL. 12:21:05 ah, ok 12:21:11 i'm not doing this very intelligently ;) 12:21:24 You are perhaps solving the wrong problems. 12:21:53 how do I know when i've run out of input? 12:22:22 BL WORD COUNT 0= IF 12:23:05 Or something of that ilk, depending on how your system handles the input buffer. I compare the value of >IN to the length of the input buffer. 12:24:25 --- quit: saon (Read error: 145 (Connection timed out)) 12:43:25 wow, thanks 12:43:26 works :D 12:52:32 --- quit: tathi ("leaving") 12:53:43 why can't my server keep good time. 12:53:56 it looses about an hour and a half every week 12:59:41 :/ 13:03:56 Temperature. 13:04:03 It's probably overheating. 13:04:44 could be, but I thought it's supposed to compensate based on how you adjust it 13:05:00 are you overclocking ? 13:05:04 no 13:05:17 i dont trust overclocking 13:36:13 It can't compensate accurately for fluctuating temperatures. 13:36:19 Best you can do is update it from the net at intervals. 13:36:58 Unless you can somehow keep the temperature around the crystal constant. 13:39:36 i might make a thermostatic-oven quartz clock 13:57:03 but it consistanly looses 1.5 hours/week 13:57:13 it never runs fast 14:03:52 Hmm, maybe you got a lemon. :) 14:10:21 But set a compensation of 1.0089285714 or so and you should be set. 14:32:03 --- join: aum (ecdd437a0c@60-234-138-239.bitstream.orcon.net.nz) joined #forth 14:34:00 --- quit: x2Sx (Read error: 60 (Operation timed out)) 14:38:19 --- join: x2Sx (~x2Sx@212.180.15.9) joined #forth 14:44:02 Quartus: What do I do with that number? 14:44:14 the first number in /etc/adjtime is 12.112172 14:47:34 Hmm, let me see. 14:49:10 Pretty sure you're not supposed to manually modify adjtime. 14:50:16 --- part: docl left #forth 14:50:54 This looks useful: http://howtos.linux.com/howtos/Clock-3.shtml 14:55:37 yeah, I found a howto 14:55:49 hi all 14:55:53 I'll try that one if the one I'm in the middle of doesn't work out 14:55:58 k 14:56:00 hi crc 14:56:52 hi crc 14:56:59 hi Quartus, Herkamire 14:58:18 http://modeemi.cs.tut.fi/~tuomov/ion/screenshots/ion2-18.png <-- some guy's ion 14:58:28 er, wrong channel 16:15:56 --- quit: SeaForth ("Leaving") 16:22:04 --- join: tkb (~tkb@dhcp-69-43-1-090.pitbpama-max5.dialup.citynet.net) joined #forth 16:36:04 --- quit: Topaz (Remote closed the connection) 16:38:47 --- quit: tkb (Read error: 60 (Operation timed out)) 16:51:57 --- quit: aum () 17:13:55 --- quit: slava ("Leaving") 17:31:18 --- join: Sonarman (~snofs@adsl-64-160-167-13.dsl.snfc21.pacbell.net) joined #forth 18:24:37 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth 18:48:39 --- quit: saon ("Lost terminal") 18:50:30 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth 20:15:24 --- join: SeaForth (~SeaForth@c-24-1-126-202.client.comcast.net) joined #forth 20:23:09 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 20:46:37 --- join: dupswapdrop (~chatzilla@c-24-118-225-27.mn.client2.attbi.com) joined #forth 20:47:42 hi there 20:47:48 Hi. 21:06:27 --- part: dupswapdrop left #forth 22:20:52 --- quit: Sonarman ("leaving") 23:12:14 --- quit: Herkamire ("off to bed") 23:59:59 --- log: ended forth/05.03.14