00:00:00 --- log: started forth/08.09.08 00:41:50 --- quit: ygrek (Remote closed the connection) 01:38:05 --- join: Myoma (n=witch@amcant.demon.co.uk) joined #forth 01:39:16 --- join: ecraven (n=nex@dyn165173.wlan.jku.at) joined #forth 02:33:13 --- join: qFox (i=C00K13S@234pc222.sshunet.nl) joined #forth 03:18:50 --- quit: proteusguy ("Leaving") 03:21:41 --- join: proteusguy (n=proteusg@61.7.144.97) joined #forth 03:26:12 --- quit: ecraven (Read error: 113 (No route to host)) 04:13:53 --- join: ecraven (n=nex@140.78.42.107) joined #forth 05:11:26 --- join: ygrek (i=user@gateway/tor/x-dfeca93092ff0f90) joined #forth 05:49:53 --- quit: ygrek (Remote closed the connection) 06:04:36 --- join: ygrek (i=user@gateway/tor/x-ee2d1bbce656b1a1) joined #forth 06:44:50 --- quit: proteusguy (Read error: 110 (Connection timed out)) 06:45:29 --- join: proteusguy (n=proteusg@ppp-124-120-227-19.revip2.asianet.co.th) joined #forth 07:13:59 --- quit: proteusguy (Read error: 110 (Connection timed out)) 07:14:46 --- join: proteusguy (n=proteusg@61.7.144.97) joined #forth 07:36:56 --- join: ASau` (n=user@77.246.231.133) joined #forth 08:00:20 --- quit: ecraven ("bbl") 08:24:03 --- quit: ASau` (Read error: 110 (Connection timed out)) 08:47:35 hi. 09:14:50 hi 09:24:40 hi. 09:29:29 hi 09:34:04 wheee! 09:34:08 anybody coding something interesting? 09:35:24 nope. 09:36:03 Well, I'm mucking around with rewriting vor in gforth... 09:37:10 :) 09:37:11 nice 09:37:35 any structural changes along the way, or mostly just a straight port? 09:38:28 only thing that pops into my head that I wish we did differently is the metric "rocks per screen" 09:39:01 I'd like to make the screen resizeable 09:46:02 I'm busy writing a bzip2 block extracter. 09:46:14 ...in, um, awk. 09:47:36 what the fawk... 09:49:06 It's the tool at hand. For a variety of reasons, there are no compilers present on the machines that hold the bzip2'd logs that require analysis and indexing, and no executables may be transferred to those machines. 09:49:13 I don't make the rules, I just avoid 'em. 09:54:43 --- join: forther (n=forther@207.47.34.100.static.nextweb.net) joined #forth 09:54:52 gnomon: weird 09:55:12 gnomon: but you can transfer awk code? 09:55:52 * JasonWoof wonders how they managed to get he logs bzip2'd 09:56:52 Using binaries that are already present on the system, and have been vetted. 09:56:59 Well, supposedly. 09:57:04 As I said, not my problem. 09:58:51 sounds like a fun project 10:00:17 It's certainly teaching me some newfound... um, respect for the bzip2 codebase. 10:00:34 bzip2recover is a bunch of bitwise read and write ops and then a 207-line main(). 10:00:51 I'm pretty sure that's illegal in most countries. 10:00:57 hehe 10:05:51 --- quit: madwork_ ("?OUT OF DATA ERROR") 10:06:15 --- join: aguai_ (n=aguai@122-116-183-8.HINET-IP.hinet.net) joined #forth 10:06:47 --- join: madwork_ (n=foo@204.138.110.15) joined #forth 10:12:10 --- quit: madwork_ ("?OUT OF DATA ERROR") 10:16:58 --- nick: aguai_ -> aguai 10:20:17 --- quit: aguai ("leaving") 10:42:35 --- join: aguai (n=aguai@122-116-183-8.HINET-IP.hinet.net) joined #forth 12:21:24 --- join: BobFunkmmm (n=mathiasc@57.pool85-61-93.dynamic.orange.es) joined #forth 12:22:15 --- nick: BobFunkmmm -> BobFunk 12:27:33 * gnomon finished up the bzip2 block extracter/indexer 12:27:43 Now to add on a random-access/seek layer... 12:33:11 --- quit: ygrek (Remote closed the connection) 12:39:46 --- quit: ramkrsna (Remote closed the connection) 12:48:52 JasonWoof: mostly just a straight port; I tend to think of Forth as being bad at math-like stuff, so I'm curious what the physics code etc. would look like... 12:49:17 cool 12:49:55 and I was curious how horribly slow it would be, and whether that would be a good motivation to actually finish my cross-compiler. :) 12:51:59 I'm curious too 12:52:06 my hunch is that it'll still be pretty fast 12:52:29 I'm worried about the particle stuff. 12:52:34 I think the bottleneck is bandwidth to the videocard 12:52:38 I did the dust first 12:52:49 2000 pixels 12:53:12 ran 100 iterations with 30 ms delays 12:53:23 and it seems to take almost 5 seconds to run. 12:54:12 Hmm...I should test it on my PPC box and see if it's slower there. 13:00:40 --- quit: qFox ("Time for cookies!") 13:37:16 --- quit: BobFunk () 13:41:56 ok, that took forever. Had to build the cvs version of gforth first. 13:42:49 Well, it is a bunch slower on the PPC box, but it's the same speed whether I actually draw anything or just clear and flip. 13:43:01 So I guess it's a video thing and not gforth. 13:43:05 Which is good. :) 13:45:09 Well, that's cool. Maybe I'll actually finish this. It would be cool to have a video game to point to when people ask what you can do in Forth. 13:46:09 --- join: BobFunk (n=mathiasc@57.pool85-61-93.dynamic.orange.es) joined #forth 13:57:39 tathi, there's always Starflight. 14:00:09 http://meusite.uai.com.br/~mmand/starflight/kernel.html 14:06:37 tathi: I couldn't get any of the sdl textures to actully live on the graphics card 14:06:44 except some rather extreeme experiments with DGA 14:06:59 (had to run it as root and get all the settings just right) 14:07:21 so I think no matter what you do, it's going to send the whole buffer to the video card every frame 14:11:38 when I did manage that, I got the game runing about 7x faster 14:43:50 --- quit: forther ("Leaving") 14:49:48 --- quit: BobFunk () 15:16:39 --- join: forther (n=forther@207.47.34.100.static.nextweb.net) joined #forth 15:44:19 JasonWoof: yeah, I remember when you were playing with that. 15:44:47 gnomon: it doesn't sound like the source code to Starflight is available... 15:50:16 It seems like occasionally people come in here and ask for examples of Forth code to look at and play with. 15:50:51 And I don't really know of anything out there that isn't either ancient or geeky little programming challenge solutions. 15:51:12 you can show them facto r:) 15:51:16 true true 15:52:08 I still think that it might be possible to do interesting things in Forth though. :) 15:52:13 sure 15:52:17 i didn't say it wasn't :) 15:52:23 nope 15:52:25 just pointing out that there's a large codebase of stack-language code 15:53:54 Yeah. I often point people at Factor, except for the wackos who have a grudge against high-level languages. 15:55:13 OK, time to go sing. 15:55:20 have fun 15:58:26 tathi, you're right - I don't think that the source code is available. The interpreter is minimal, however, and can be thrown into an interactive state relatively easily. 15:59:35 Also, some of the source code was released; it is available over at http://www.geocities.com/TimesSquare/Maze/4979/lee.html (look to the bottom of the page). 16:32:15 --- part: forther left #forth 17:59:32 --- quit: aum ("Leaving") 19:07:03 --- quit: proteusguy (Read error: 110 (Connection timed out)) 19:07:53 --- join: proteusguy (n=proteusg@61.7.144.97) joined #forth 22:32:56 --- join: aum (n=aum@60-234-243-247.bitstream.orcon.net.nz) joined #forth 23:12:05 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 23:29:15 --- join: ASau` (n=user@host3-231-msk.microtest.ru) joined #forth 23:38:38 --- join: BobFunk (n=mathiasc@57.pool85-61-93.dynamic.orange.es) joined #forth 23:43:57 --- quit: BobFunk () 23:53:50 --- join: BobFunk (n=mathiasc@57.pool85-61-93.dynamic.orange.es) joined #forth 23:59:59 --- log: ended forth/08.09.08