00:00:00 --- log: started forth/08.01.27 00:02:30 --- join: ygrek (i=user@gateway/tor/x-ca6a17c2b17a0382) joined #forth 00:33:24 --- quit: ygrek (Remote closed the connection) 00:34:25 --- join: ygrek (i=user@gateway/tor/x-48ded36a6bc383d6) joined #forth 01:13:07 --- join: viperhr (n=viper@chello084114184044.13.15.vie.surfer.at) joined #forth 01:13:07 --- mode: ChanServ set +b *!*v*@*.vie.surfer.at 01:13:07 --- part: viperhr left #forth 01:14:11 --- join: viperhr (n=xiper@chello084114184044.13.15.vie.surfer.at) joined #forth 01:15:14 did i get banned for a specific reason? 01:53:19 yes, we thought you were virl 01:55:19 don't worry, i'm not.. who's virl? 01:55:39 somebody on the same isp 02:22:06 ic, ok 04:26:21 --- join: TalkSoup (n=todd@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 04:28:45 --- nick: TalkSoup -> Not-Al2O3 05:51:14 --- quit: Not-Al2O3 (Remote closed the connection) 07:19:42 --- join: swestres (n=hihihi@Doc-14-47.veberod.com) joined #forth 07:21:12 ! If my Forth interpreter uses WORD for the outer interpreter, then it won't make much sense using it when interpreting 07:23:05 Since: 32 WORD blabla COUNT TYPE will print TYPE becase the internal WORD buffer will be overwritten by the outer interpreter calling WORD 07:23:49 But the ANS draft doesn't say that the interpretation behaviour is undefined, so my question is (finally) is there any use for WORD in interpretation mode? 07:24:25 because I'm kinda thinking of restricting it to a compile-time only word 09:36:59 Then it won't be standard. 09:38:27 WORD will probably not be the best fit for building a standard parser, at any rate. 09:39:06 Even if you wedge it in that way, it's such a simple word you can provide a version that uses a different buffer in source, optionally loadable. 09:57:20 --- join: tgunr (n=davec@70-41-253-101.cust.wildblue.net) joined #forth 10:18:19 --- quit: Quartus () 10:43:33 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 10:43:33 --- mode: ChanServ set +o Quartus 10:46:48 Quartus: Why is WORD not good for a parser? 10:49:18 It copies to a counted-string buffer; it's really only there for historical reasons. The PARSE-WORD discussed in the appendix of the Standard is a better choice. 10:52:20 Ah, I see. Thanks :) 10:52:40 Sure. 11:13:57 If I have a string like cccc, is >IN set to the offset of by PARSE, or is it set to the offset of +1? 11:14:21 two ways to find out: read the standard semantics, and/or test it in Gforth. 11:15:01 PARSE is not an adequate tool for the interpreter's main loop -- you really want PARSE-WORD as described in the appendix. 11:15:31 I can't find anything about it in the ANS draft (the space thing i.e.), I just thought you might know. 11:16:02 PARSE-WORD is just : PARSE-WORD 32 PARSE ; if I'm not mistaken? 11:19:41 No. http://quartus.net/dpans/dpansa6.htm#A.6.2.2008 11:20:11 if I remember correctly - PARSE-NAME is a preferred name 11:20:17 by 200x 11:20:28 That's what 200x came up with. 11:20:36 The Standard doc talks about it as parse-word. 11:22:52 I have the draft, but I still don't see why PARSE-WORD is not : PARSE-WORD 32 PARSE ; . What's different? 11:23:43 parse-word skips leading delimiters. 11:24:38 Oh, sorry 11:55:06 --- join: Guest9548915 (i=snoopy_1@dslb-088-068-195-235.pools.arcor-ip.net) joined #forth 12:03:19 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 12:03:19 --- nick: Guest9548915 -> Snoopy42 12:41:46 --- quit: Quartus () 12:55:00 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 12:55:00 --- mode: ChanServ set +o Quartus 13:42:10 --- quit: ygrek (Remote closed the connection) 13:47:50 --- quit: viperhr ("Leaving") 13:54:46 --- quit: Al2O3 (Connection reset by peer) 13:54:53 --- join: sauvin (n=sauvin@74-136-191-102.dhcp.insightbb.com) joined #forth 13:54:58 --- join: X-Scale (n=none@89.181.56.39) joined #forth 13:55:25 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 13:58:59 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 13:59:00 --- mode: ChanServ set +o tathi 14:01:32 --- join: d_schauer (n=dwight@cpe-76-187-164-188.tx.res.rr.com) joined #forth 14:16:26 --- part: d_schauer left #forth 14:25:53 --- quit: Al2O3 (Client Quit) 14:26:15 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 14:33:39 --- quit: Al2O3 (Remote closed the connection) 14:34:00 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 15:01:35 --- join: I440r (n=mark4@63-229-121-90.phnx.qwest.net) joined #forth 15:02:27 --- mode: ChanServ set +o I440r 15:03:05 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 15:08:34 anyone here familiar with doing DOS coding still? 15:09:37 I've played a little with BIOS interrupts in 16-bit real mode on an IA-32, does that count? 15:10:21 well... im having issues with the dos allocation call 15:10:34 i allocate memory. verify that the allocationw as successfull and... 15:10:41 if i modify MY MEMORY my app crashes 15:10:59 doing a dump of said memory shows the first 256 bytes to be constantly changing 15:11:12 i.e. the memory that the system allocated TO ME is in use 15:11:23 this is in a windows xp dos box 15:11:28 so i think windows xp is fucking with me 15:15:26 --- quit: I440r ("Leaving") 15:15:27 Sorry, can't help :\ 15:15:54 xp's dos box is an emulator, it may not be 100% accurate... 15:24:53 --- join: I440r (n=mark4@63-229-121-90.phnx.qwest.net) joined #forth 15:41:15 --- join: I440r_ (n=mark4@63-229-121-90.phnx.qwest.net) joined #forth 16:04:08 --- quit: I440r (Read error: 110 (Connection timed out)) 16:09:26 --- join: Quartus__ (n=Quartus_@209.167.5.2) joined #forth 16:24:43 --- quit: sauvin (Read error: 104 (Connection reset by peer)) 16:30:31 --- quit: Quartus__ ("used jmIrc") 16:30:47 --- join: Quartus__ (n=Quartus_@209.167.5.2) joined #forth 17:40:43 --- quit: tathi (Read error: 110 (Connection timed out)) 18:12:45 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 19:27:33 --- join: arke_ (n=arke@p54A7C7DE.dip.t-dialin.net) joined #forth 19:44:25 --- quit: arke (Read error: 110 (Connection timed out)) 20:17:53 --- quit: X-Scale (Connection timed out) 21:10:58 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 22:00:37 --- nick: arke_ -> arke 22:12:47 --- quit: proteusguy (Success) 22:13:27 --- join: proteusguy (n=proteusg@ppp-124.120.229.32.revip2.asianet.co.th) joined #forth 22:20:36 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 22:33:04 --- quit: proteusguy (Connection reset by peer) 22:43:53 --- join: proteusguy (n=proteusg@ppp-124-121-211-66.revip2.asianet.co.th) joined #forth 23:02:19 --- join: awg` (i=[xkxOHxw@panix5.panix.com) joined #forth 23:04:19 --- part: awg` left #forth 23:25:53 --- quit: I440r_ (Read error: 110 (Connection timed out)) 23:27:31 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 23:45:10 --- join: I440r (n=mark4@63-229-121-90.phnx.qwest.net) joined #forth 23:59:59 --- log: ended forth/08.01.27