00:00:00 --- log: started forth/06.04.12 00:01:09 --- quit: segher (Read error: 110 (Connection timed out)) 01:04:36 --- join: Cheery (i=Henri@a81-197-60-217.elisa-laajakaista.fi) joined #forth 01:42:12 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 01:43:04 hi 01:50:33 --- quit: Alterego (Remote closed the connection) 02:06:18 --- join: snoopy_1711 (i=snoopy_1@84.58.115.231) joined #forth 02:12:48 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 02:13:00 --- nick: snoopy_1711 -> Snoopy42 02:40:22 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 03:12:36 --- quit: arke (zelazny.freenode.net irc.freenode.net) 03:12:36 --- quit: crc (zelazny.freenode.net irc.freenode.net) 03:12:37 --- quit: slava (zelazny.freenode.net irc.freenode.net) 03:12:37 --- quit: Zymurgy (zelazny.freenode.net irc.freenode.net) 03:14:25 --- join: arke (i=c_walton@lnx103.hrz.tu-darmstadt.de) joined #forth 03:14:25 --- join: crc (i=crc@pool-70-110-130-229.phil.east.verizon.net) joined #forth 03:14:25 --- join: Zymurgy (i=zymurgy@cat.delfax.net) joined #forth 03:14:29 --- quit: arke (Remote closed the connection) 03:14:29 --- join: slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 03:14:31 --- join: arke (i=c_walton@lnx103.hrz.tu-darmstadt.de) joined #forth 03:14:40 --- quit: Zymurgy (Remote closed the connection) 03:14:45 --- join: Zymurgy (i=zymurgy@cat.delfax.net) joined #forth 04:19:02 --- quit: crc (zelazny.freenode.net irc.freenode.net) 04:19:19 --- join: crc (i=crc@pool-70-110-130-229.phil.east.verizon.net) joined #forth 04:31:35 hi crc 05:02:54 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 05:19:30 --- join: scope (i=scope@narcotics.school.nz) joined #forth 05:42:14 --- quit: tathi ("leaving") 05:43:11 --- join: PoppaVic (n=pete@0-1pool75-157.nas24.chicago4.il.us.da.qwest.net) joined #forth 07:29:51 --- quit: PoppaVic (Nick collision from services.) 07:30:09 --- join: PoppaVic (n=pete@0-1pool75-189.nas24.chicago4.il.us.da.qwest.net) joined #forth 07:34:32 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 07:34:32 --- mode: ChanServ set +o JasonWoof 07:44:05 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 08:08:18 --- quit: PoppaVic ("Pulls the pin...") 08:17:30 --- quit: moreCowbell ("Computer goes to sleep!") 08:40:01 --- join: PoppaVic (n=pete@0-1pool72-156.nas24.chicago4.il.us.da.qwest.net) joined #forth 08:41:05 tathi: hey! ;-) 08:50:22 hi 08:50:41 I've been cogitating... 08:51:36 http://rafb.net/paste/results/X0Wu7J65.html 08:52:05 I'm still trying to sorta' reconcile names/heads, wordlists, and states. 08:53:11 I am sorta' in a quandry over STATE, headers, wordlists, and bodies/activities. 08:53:28 above is mostly "classic Forth". 08:55:53 Where it all gets foggy seems to be treating a boolean 'state' as 2 flags of 4 states, and then what a header or a body means. 08:57:01 I think we are seeing a lot of mixing of a "dual-state-machine" with a lot of higher interpreters/machine-states. 08:59:31 Also... and this is going to sound weird... the idea of Cell or xt_t (types) seems to mean more of a high-level-Interpretation than binary/machine. 09:01:45 What I _think_ I am seeing is the interfacial-space between C and Forthish - a mixture of ABI's/interpreters/data 09:03:48 And -regardless of processor- we seem to be dealing with C-like integral-types verses interspacial values (pointers or literals) 09:09:07 --- quit: neceve ("Bye people, I'm leaving") 09:13:51 tathi: I know there are a few "magic-numbers" floating around, and that VM is not complete. 09:18:09 --- join: Alterego (n=Alterego@88.202.136.178) joined #forth 10:54:02 --- quit: PoppaVic ("Pulls the pin...") 11:19:47 --- nick: Raystm2 -> NANSTM 12:13:47 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-166-042.pools.arcor-ip.net) joined #forth 12:22:33 --- quit: madwork (Read error: 104 (Connection reset by peer)) 12:22:34 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 12:22:35 --- nick: snoopy_1711 -> Snoopy42 12:26:39 --- join: madwork (n=foo@derby.metrics.com) joined #forth 12:28:04 PING 12:37:39 --- quit: Cheery ("Leaving") 12:47:35 --- join: Ray_work (n=Raystm2@adsl-68-90-192-85.dsl.rcsntx.swbell.net) joined #forth 12:47:36 --- quit: Ray-work (Read error: 104 (Connection reset by peer)) 13:12:01 --- join: Raystm2 (n=Raystm2@adsl-69-149-46-83.dsl.rcsntx.swbell.net) joined #forth 13:12:18 --- quit: NANSTM (Read error: 104 (Connection reset by peer)) 13:27:06 hi 14:09:36 --- join: Lars_G (n=lars@unaffiliated/lars-g/x-000001) joined #forth 15:55:03 --- quit: Alterego (Remote closed the connection) 17:05:24 --- quit: tathi ("leaving") 17:14:06 --- part: Lars_G left #forth 18:16:35 --- join: brasshopper (n=njs@glock.squawk.com) joined #forth 18:18:40 I have not actually written a forth program since the mid 1980's when you coud get Forth on a diskette for an S-100 system. I tried to make gforth on Fedora Core 5 and it dies with "Cannot allocate memory". Is there some magic to making gforth work on recent linux, or a better forth to use to get restarted? 18:19:46 That's a known build issue, it's documented on the gforth page. 18:19:55 Let me see if memory serves. 18:20:17 I'll go and look then, sorry, unless you want to hold forth as it were. 18:21:05 What's the exact message? What version of Gforth? 18:21:44 --- join: Robert___ (n=robert@ua-83-227-163-7.cust.bredbandsbolaget.se) joined #forth 18:22:00 gforth 0.6.1 18:22:19 Why not 0.6.2? 18:22:51 I enter the bare command ./gforth-fast and the response is ./gforth-fast: Cannot allocate memory 18:23:02 Oh, so you've built it successfully. 18:23:13 What about just ./gforth? 18:23:53 --- quit: Robert___ (Client Quit) 18:24:03 As far as I can tell that was the most recent version on the gnu miror I looked at. 18:24:14 http://www.jwdt.com/~paysan/gforth.html#CHANGES 18:24:28 sorry, http://www.jwdt.com/~paysan/gforth.html 18:24:48 I will look for 0.6.2 on a different mirror. Yes, I just did ./configure and then make - I tried make test and some worked, some gave me that error. 18:24:49 User-visible changes between 0.6.1 and 0.6.2: 18:24:49 Bug fixes 18:24:49 (in particular, gforth-0.6.2 compiles with gcc-3.3) 18:25:10 4OK, I'll look for the more recent version and see what happens 18:25:21 There are also various precompiled binaries. 18:27:25 ftp://gatekeeper.dec.com/pub/GNU/gforth (typed by hand) has 0.6.1 as the most recent version. That happened to be the site I looked at 18:28:32 --- quit: Robert (Read error: 110 (Connection timed out)) 18:28:42 Unless I can get an RPM there is no particular advantage to precompiled I would think. 18:29:06 UFL has 0.6.2 - so it looks like gatekeeper is not up to date - sad. 18:29:45 thanks for the help - I'll go off and build this now, 18:33:26 Well, it did not help as much as I hoped - same error. Either ./gforth or ./gforth-fast gives me the "Cannot allocate memory" error. 18:34:18 I have plenty of memory and swap - the error happens almost instantly upon entering the command. 18:34:28 --- quit: uiuiuiu (Remote closed the connection) 18:34:32 --- join: uiuiuiu (i=ian@dslb-084-056-234-112.pools.arcor-ip.net) joined #forth 18:34:36 make test actually has some of the tests running. 18:35:22 I'll tgo and look at the web page you mentioned earlier 18:48:45 OK, I downloaded the prebuilt binary and expanded it into /tmp - first thing it complained about was not being able to find gforth.fi in any of a list of odd places. So I looked and found that while gforth.fi was not in the binary I had just downloaded, it was in the source I had downloaded before. I copied the 0.6.2 version into the current directory (on a hunch) and it then gave me the "Cannot allocate memory" error I had earlier - so it is likely 18:48:45 not my compiler. 18:54:15 Or, for that matter, the way I am building it...since in this case it was not me - gforth.fi seems to be a very short file which has an incorrect "please feed this to this binary" line and then a line that says " Gforth3^E" where that is a control-E 19:02:17 OK, that seems to help - and this is odd. I recompiled after applying the patch for exec-shield in known-problems.html - that fix application cures the issue of "can't allocate memory". The binary package does not, I don't get it. 19:03:27 I can at least make test and make bench now. 19:04:11 So thanks for pointing me to 0.6.2 and to the site. 19:44:06 --- quit: saon (Read error: 110 (Connection timed out)) 19:57:02 Sure, no worries. 20:08:44 --- quit: scope ("Client exiting") 20:15:05 --- join: saon (i=1000@c-66-177-224-164.hsd1.fl.comcast.net) joined #forth 22:41:41 --- quit: JasonWoof ("off to bed") 22:49:21 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 22:49:21 --- mode: ChanServ set +o JasonWoof 22:49:25 --- quit: JasonWoof (Client Quit) 23:59:59 --- log: ended forth/06.04.12