00:00:00 --- log: started forth/10.12.03 00:08:21 --- part: ixor left #forth 01:45:37 --- quit: mathrick (Ping timeout: 240 seconds) 01:47:00 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 02:20:00 --- join: geo (~color@athedsl-115391.home.otenet.gr) joined #forth 02:20:28 --- part: geo left #forth 03:01:38 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 03:46:45 --- quit: gogonkt (Ping timeout: 240 seconds) 04:31:26 --- join: gogonkt (~info@113.105.207.246) joined #forth 05:10:15 --- quit: gogonkt (Read error: Connection reset by peer) 05:23:42 --- join: gogonkt (~info@113.105.207.246) joined #forth 05:35:03 --- quit: MayDaniel (Read error: Connection reset by peer) 06:42:47 --- quit: ASau (Remote host closed the connection) 06:43:40 --- join: ASau (~user@95-28-62-161.broadband.corbina.ru) joined #forth 07:31:28 --- join: apropos (~apropos@89-168-180-93.dynamic.dsl.as9105.com) joined #forth 07:31:34 What does & do in Forth? 07:33:20 It seems to just push a 0. 07:37:06 Nothing, neither in standard nor in tradition. 07:37:27 What are you using? 07:37:55 that's actually interesting with gforth 07:37:59 & => 0 07:38:03 but there is no & word 07:38:10 apropos: Are you bug hunting? :) 07:38:17 :1: Undefined word 07:38:17 >>>&<<< 07:38:17 Backtrace: 07:38:17 $BB504FE4 throw 07:38:20 $BB5119F8 no.extensions 07:38:23 $BB5051A4 interpreter-notfound1 07:38:23 not here. 07:38:26 Not here. 07:38:32 see & gives me dat undefined word 07:38:37 but just & does indeed push 0 07:38:38 Oh. 07:38:46 Perhaps you're using some buggy old gforth. 07:38:49 .7.0 07:38:52 could be old and buggy, ya. 07:39:00 0.7.0. Hmm, yes 07:39:06 apropos: x86-64 ? 07:39:10 Yes 07:39:11 gforth-0.7.99nb20101125 07:39:13 interesting. 07:39:35 That is CVS from 2010-11-25. 07:39:51 apropos: I guess you will contact the gforth people and see if this bug has been reported :) 07:40:04 I suspect that this is bug in number parser. 07:40:12 sounds likely. 07:41:37 Hmm, &1 pushes 1, &2 pushes 2 etc. 07:42:01 Gforth allows you to override the value of `base' by using a 07:42:01 prefix(2) before the first digit of an (integer) number. The following 07:42:01 prefixes are supported: 07:42:01 * `&' - decimal 07:42:16 Definitly bug in number parser. 07:42:16 apropos: yes. The number parsing :) just & by itself shouldn't behave like &0 07:42:20 Update to CVS snapshot. 07:42:50 schmrkc: this is disputable. 07:43:00 Everything is disputable. 07:43:30 Unfortunatly this behaviour is in standard. 07:43:36 At least for FPN. 07:43:46 cools. 07:44:05 See 12.6.1.0558 07:44:07 I think its stupid behaviour. 07:45:14 So if this behaviour is good, why is it then removed in your cvs snapshot? 07:46:21 I don't think it is stupid. 07:46:25 I think that it's idiotic. 07:46:46 That too. 07:47:46 It is another case of minute ad hoc convenience vs. consistency. 07:48:27 It's totally idiotic. 07:49:32 well pancakes 07:49:38 --- quit: Deformative (Ping timeout: 240 seconds) 08:03:58 --- quit: segher (Ping timeout: 240 seconds) 08:08:33 --- join: segher (~segher@5ED3C3A7.cm-7-4d.dynamic.ziggo.nl) joined #forth 08:14:29 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 08:17:53 --- join: qFox (~C00K13S@5356B263.cm-6-7c.dynamic.ziggo.nl) joined #forth 08:21:35 --- part: apropos left #forth 08:28:18 --- quit: MayDaniel (Ping timeout: 240 seconds) 08:33:41 --- quit: ASau (Remote host closed the connection) 08:34:34 --- join: ASau (~user@95-28-62-161.broadband.corbina.ru) joined #forth 08:35:52 --- join: Deformative (~Joseph@67-194-79-214.wireless.umnet.umich.edu) joined #forth 09:26:06 --- quit: Deformative (Ping timeout: 245 seconds) 10:36:01 --- join: Deformative (~Joseph@141.212.208.134) joined #forth 10:36:38 --- quit: mathrick (Ping timeout: 240 seconds) 11:16:18 --- join: kar8nga (~kar8nga@m-215.vc-graz.ac.at) joined #forth 11:30:38 --- quit: Deformative (Ping timeout: 250 seconds) 12:19:25 --- join: scott0070 (~scott@user-24-96-104-124.knology.net) joined #forth 12:23:32 --- join: Deformative (~Joseph@caen-cse-141-212-202-92.wireless.engin.umich.edu) joined #forth 12:39:30 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 12:49:35 --- quit: MayDaniel (Read error: Connection reset by peer) 13:12:10 crc, has retro been tested with clang? 13:12:45 --- quit: qFox (Quit: Time for cookies!) 13:19:40 --- join: Deformati (~Joseph@caen-cse-141-212-202-92.wireless.engin.umich.edu) joined #forth 13:22:06 --- quit: Deformative (Ping timeout: 240 seconds) 13:31:20 --- quit: Deformati (Read error: Connection reset by peer) 13:36:21 appamatto: pforth has been tested with it. 13:37:59 --- join: Deformative (~Joseph@caen-cse-141-212-202-92.wireless.engin.umich.edu) joined #forth 13:49:03 yeah, looks like retro also works with clang 13:49:09 clang is the future baby 14:06:53 Eh. 14:06:56 Clang is a parser. 14:07:16 Parsers hardly can be considered a future or a present. 14:07:19 They are so replacable. 14:16:32 appamatto: I've built retro with gcc, pcc, clang-llvm, and gcc-llvm 14:18:30 crc, yeah I noticed after I asked you that there is very little c code 14:18:50 all of the vm implementations are small 14:30:33 Previous pcc doesn't handle pforth. 14:30:43 Maybe they've fixed it in 0.9.9... 14:33:33 Hm. They fixed it in 0.9.9.20 15:57:55 --- quit: kar8nga (Remote host closed the connection) 16:30:40 --- quit: scott0070 (Ping timeout: 255 seconds) 16:43:09 --- join: scott0070 (~scott@207.98.152.197) joined #forth 17:26:28 --- quit: Deformative (Ping timeout: 255 seconds) 17:49:43 --- quit: scott0070 (Ping timeout: 264 seconds) 18:05:36 --- join: scott0070 (~scott@207.98.152.197) joined #forth 18:40:16 --- join: Deformative (~Joseph@205-36.adsl.umnet.umich.edu) joined #forth 19:58:34 --- quit: scott0070 (Quit: Leaving) 23:58:16 --- join: qFox (~C00K13S@5356B263.cm-6-7c.dynamic.ziggo.nl) joined #forth 23:59:59 --- log: ended forth/10.12.03