00:00:00 --- log: started forth/11.10.29 00:13:57 --- join: MoALTz (~no@host-92-18-7-192.as13285.net) joined #forth 01:04:37 --- quit: ygrek (Ping timeout: 248 seconds) 02:25:17 --- join: ygrek (~user@gateway/tor-sasl/ygrek) joined #forth 02:43:33 --- join: Bahman (~Bahman@2.145.231.19) joined #forth 02:44:02 Hi all! 03:20:40 --- quit: ttmrichter (Ping timeout: 244 seconds) 03:22:10 --- quit: ygrek (Ping timeout: 248 seconds) 03:22:21 --- join: ttmrichter (~ttmrichte@221.234.39.203) joined #forth 03:32:18 --- quit: karswell (Ping timeout: 240 seconds) 03:34:12 --- join: ygrek (~user@gateway/tor-sasl/ygrek) joined #forth 03:59:47 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 04:00:50 --- join: karswell (~coat@93-97-29-243.zone5.bethere.co.uk) joined #forth 05:07:13 --- join: xpololz (~xpololz@dhcp232-stud.wifi.uit.no) joined #forth 06:04:22 --- quit: MayDaniel (Read error: Connection reset by peer) 06:09:15 Ahoy-o, Bahman. 06:09:25 You'll notice that this channel is a bit slow-motion. :) 06:17:08 --- quit: xpololz (Quit: Leaving) 06:21:10 --- quit: ygrek (Remote host closed the connection) 06:26:07 --- join: ygrek (~user@gateway/tor-sasl/ygrek) joined #forth 06:45:30 Hey ttmrichter! Yes...already noted :-) 06:54:30 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 06:58:16 So what questions did you have today, Bahman? 06:58:55 Nothing yet...In fact I'm starting to understand Forth core code (using SEE) :-) 06:59:48 That gets a bit limited when you start hitting the words implemented in assembler. 07:00:35 Sure it will. 07:00:44 But so far so good. 07:03:38 You could look at an implementation or ten too. :) 07:10:08 --- quit: Fox78 (Read error: Connection reset by peer) 07:10:34 --- join: Fox78 (~fox@123.121.56.192) joined #forth 07:10:35 Not so fast...I'm just reading chapter 8 of "Starting Forth" but maybe you're right...the best way is to read the code. 07:22:28 Starting Forth is a great way to get the concepts down pat. 07:22:41 Then look at an implementation to persuade yourself just how simple Forth really is at its core. 07:22:50 (It's like Lisp in this regard: almost laughably simple at its core.) 07:23:43 Aha...thanks for the hint. 07:52:23 --- quit: ttmrichter (Quit: Leaving) 08:34:12 --- quit: Bahman (Ping timeout: 240 seconds) 08:48:21 --- join: Bahman (~Bahman@2.146.67.158) joined #forth 09:21:39 --- join: xpololz (~xpol@50.80-203-124.nextgentel.com) joined #forth 09:44:44 --- quit: MayDaniel (Read error: Connection reset by peer) 10:11:21 --- quit: xpololz (Ping timeout: 240 seconds) 10:27:23 --- join: nighty- (~nighty@69-165-220-105.dsl.teksavvy.com) joined #forth 10:32:13 --- quit: nighty- (Remote host closed the connection) 11:37:07 --- join: xpololz (~xpol@50.80-203-124.nextgentel.com) joined #forth 12:45:00 Whenever I use PAD SOMEWORD if SOMEWORD is not in Forth (i.e. it's in Assembly) gForth hangs like below: 12:45:10 see aligned 12:45:10 Code aligned 12:45:25 Would anyone please shed a light? 12:49:07 --- quit: xpololz (Quit: Leaving) 12:57:41 Bahman: are you using a 64-bit gforth? 13:02:19 crc: Yes. 13:02:28 Is that the problem? 13:02:34 yes 13:02:54 I see. Are there any workarounds or that's the way it is? 13:02:59 32-bit builds seem to work ok, but the decompiler for code words is broken on 64-bit 13:03:48 Alright...thank you. 13:04:21 So it's not possible at all to see the code for some words on 64 bit builds? 13:06:30 there's a patch mentioned at http://groups.google.com/group/comp.lang.forth/msg/0563d12d079e25f3 that may help 13:07:53 Thank you crc. 13:19:02 One other question...reading "Starting Forth" chapter 9 exercise 9-4, the following two phrases should yield the same value 13:19:06 DATE . 13:19:11 ' DATE . 13:19:24 Assuming DATE has been defined using VARIABLE... 13:19:31 but I get two different values for each. 13:19:34 What am I missing? 13:22:15 date . --> date gets executed, returning the address of the contents of the variable 13:22:15 ' date . --> displays the address (xt) of the code corresponding to the date function 13:22:20 e.g., ' date execute . 13:22:32 should display the same as date . 13:23:07 or ' date >body . 13:24:08 (it's worth noting that starting forth is pretty old; the internal design of various forth systems doesn't necessarily match the internals assumed by the text these days) 13:37:32 Thanks again crc...You're right. I just stumbled upon another inconsistency...assuming the word TEST as below: 13:37:41 : TEST ." sample " ; 13:38:07 The phrase ' TEST >BODY CELL+ 1+ 7 TYPE should print 'sample' but it doesn't... 13:38:40 With a bit of trial and error I figured out that 1+ is not correct and on my system I should use 8 + for it to work. 13:39:02 Though I don't have any idea what 8 is for :-) 13:50:28 I have no idea what gforth's compiler generates 14:20:15 --- join: tathi (~josh@dsl-216-227-119-9.fairpoint.net) joined #forth 14:20:38 Hi all 14:38:14 Hi tathi! 14:43:11 --- quit: Bahman (Quit: Leaving.) 14:45:16 --- join: Bahman (~Bahman@2.146.67.158) joined #forth 14:52:02 --- quit: ygrek (Ping timeout: 248 seconds) 15:06:03 --- quit: Bahman (Ping timeout: 240 seconds) 15:43:21 --- quit: MoALTz (Read error: Connection reset by peer) 15:43:59 --- join: MoALTz (~no@host-92-18-7-192.as13285.net) joined #forth 16:06:52 --- quit: nighty^ (Ping timeout: 260 seconds) 16:07:08 --- join: nighty^ (~nighty@69-165-220-105.dsl.teksavvy.com) joined #forth 16:32:05 --- join: Bahman (02929769@gateway/web/freenode/ip.2.146.151.105) joined #forth 17:14:36 --- quit: Bahman (Quit: Page closed) 17:17:05 --- join: Bahman (~Bahman@2.146.151.105) joined #forth 17:33:03 --- join: Bahman_ (02929769@gateway/web/freenode/ip.2.146.151.105) joined #forth 17:33:15 --- quit: Bahman (Quit: Leaving.) 17:51:18 --- nick: Bahman_ -> Bahman 17:54:57 --- quit: Bahman (Quit: Page closed) 17:56:44 --- join: Bahman (02929769@gateway/web/freenode/ip.2.146.151.105) joined #forth 18:32:00 --- join: ttmrichter (~ttmrichte@61.184.205.202) joined #forth 19:43:29 --- quit: Bahman (Quit: Page closed) 20:08:09 --- quit: angstrom (Ping timeout: 240 seconds) 20:09:10 --- join: angstrom (~Unknown@unaffiliated/angstrom) joined #forth 23:24:08 --- quit: ttmrichter (Read error: Connection reset by peer) 23:59:59 --- log: ended forth/11.10.29