00:00:00 --- log: started forth/13.02.08 00:00:12 that's an interesting idea 00:01:19 started after reading martin fowler's book "refactoring", and daniel quinn's "ishmael" 00:07:35 anyway, i'm out.have a good day/night everybody. 00:07:39 --- nick: tangentstorm -> tangentsleep 00:07:50 thanks, tangentstorm! I'll have to take some time and study this stuff... 01:07:05 --- quit: impomatic (Ping timeout: 252 seconds) 01:48:10 --- join: nighty^ (~nighty@90.84.144.27) joined #forth 02:04:24 --- join: snowrichard (~richard@206.255.124.206) joined #forth 02:04:51 hello 02:06:32 --- quit: cataska (Quit: ERC Version 5.3 (IRC client for Emacs)) 02:06:55 --- quit: snowrichard (Client Quit) 05:32:38 --- join: karswell (~user@93-97-29-243.zone5.bethere.co.uk) joined #forth 06:36:00 --- nick: tangentsleep -> tangentstorm 08:50:37 --- join: Tod-Work (~thansmann@host-25.pl1071005.fiber.net) joined #forth 09:15:02 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 09:33:22 --- join: ASau (~user@46.115.44.118) joined #forth 09:33:22 --- join: ncv (~quassel@79.114.100.201) joined #forth 09:33:22 --- quit: ncv (Changing host) 09:33:22 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 09:49:07 --- join: ncv_ (~quassel@86.125.253.58) joined #forth 09:51:55 --- quit: ncv (Ping timeout: 252 seconds) 10:15:55 --- join: dto (~user@pool-96-252-62-13.bstnma.fios.verizon.net) joined #forth 10:43:38 --- quit: dto (Remote host closed the connection) 11:21:13 --- join: impomatic (~digital_w@65.30.113.87.dyn.plus.net) joined #forth 11:37:41 --- quit: karswell (Remote host closed the connection) 11:38:37 --- join: karswell` (~user@93-97-29-243.zone5.bethere.co.uk) joined #forth 11:41:03 --- join: epicmonkey (~epicmonke@sabis.ru) joined #forth 12:25:29 --- join: Nisstyre-laptop (~yours@oftn/member/Nisstyre) joined #forth 12:29:58 --- quit: sirdancealot1 (Ping timeout: 255 seconds) 12:34:44 --- join: sirdancealot1 (~sirdancea@98.82.broadband5.iol.cz) joined #forth 12:59:57 --- join: JDat (JDat@89.248.91.5) joined #forth 13:09:55 --- quit: epicmonkey (Ping timeout: 255 seconds) 13:15:23 --- nick: kulp -> avoscadeaux 13:28:05 --- join: RodgerTheGreat (~rodger@71-13-216-83.dhcp.mrqt.mi.charter.com) joined #forth 13:29:15 --- join: rbarraud__ (~rbarraud@125-239-32-133.jetstream.xtra.co.nz) joined #forth 13:31:01 what's goin' on, everybody? 13:36:25 waiting to go home from work :) 13:36:33 yourself ? 13:36:35 way ahead of you 13:36:39 --- quit: tgunr (Ping timeout: 240 seconds) 13:36:49 I had another goofy idea for a video game 13:37:11 do tell 13:37:12 I think I've outdone myself on designing a puzzle game that only four or five people on earth could play 13:37:21 "F18 Combat Simulator" 13:37:35 it would be sort of like corewars except on a virtual GA144 13:38:00 and rather than trying to overwrite or crash enemy programs the goal is to play "capture the flag" 13:38:19 you start on corners of the chip and near the opposing team there is an IO port 13:38:35 if you read from it, you'll get a machine word ("the flag") 13:38:46 if you write that word to your own IO port ("the goal") 13:38:48 you score 13:39:06 and if you write something else to your goal it'll block for a while 13:39:33 avoscadeaux: thoughts 13:40:34 --- join: tgunr (~davec@cust-66-249-166-11.static.o1.com) joined #forth 13:41:33 I think this would be an interesting context within which to tackle and get used to the strange and powerful potential the chip has for self-modifying code 13:41:39 haha wow 13:41:53 also I think the title is amusingly misleading 13:42:03 yeah i don't get it 13:42:32 well there's a plane called the F18: http://en.wikipedia.org/wiki/F/A-18_Hornet 13:42:33 i've never played corewars but i eventually want to implement one on my chip 13:42:35 right 13:42:41 i don't see how it's connected 13:42:48 but individual cores on a GA144 are also called F18s 13:42:56 in that case because they are 18-bit forth machines 13:43:03 oho 13:43:24 is there a GA144 simulator already 13:43:33 there is, but it's part of colorforth 13:43:37 i would imagine such a thing would be a huge boon for the developers so it either should or does 13:43:40 ah 13:43:41 I was thinking about writing my own 13:43:48 ambitious 13:43:58 I have written a (buggy) simulator for a single F18 core before 13:44:00 then again if the cores are simple enough it might not be that hard 13:44:08 and they do have very good docs available 13:44:10 i don't really know anything about the architecture 13:44:13 except broad strokes 13:44:20 basically you have a grid of F18s 13:44:34 they can handshake with their neighbors 13:44:40 otherwise they are clockless 13:44:49 yeah 13:44:54 F18s on the edges communicate with IO devices 13:45:15 individual cores have 64 words of ram and 64 words of rom 13:45:28 words being 18 bits wide ? 13:45:34 machine words are 18 bits and the instruction encoding allows up to four instructions per word 13:45:43 isn't it like bundles of words in 18 bits like 5 5 5 3 or something 13:45:47 yeah 13:45:54 err bundles of instructions 13:46:01 the last slot can only hold a subset of the opcode list 13:46:11 yeah i remember reading that now, i guess i read more than i thought 13:46:22 then it has a 10(?) word pstack and 8(?) word rstack 13:46:24 i wish i knew how to program the thing 13:46:28 then again so does everyone 13:46:28 ;) 13:46:29 that are cyclic 13:46:48 take the course, avoscadeaux 13:46:54 I get the impression they are internally shift registers 13:47:19 tangentstorm: good idea, but really what i mean is that i wish i knew how to think about concurrency 13:47:36 two registers which are for memory ops and a third for controlling the IO ports 13:47:37 i've managed to remain single-threaded my whole (short) career so far, with very minor exceptions 13:47:42 http://school.arrayforth.com/ 13:48:01 intersting 13:48:05 interesting, too. 13:48:05 you've never written a shell script with a pipe? 13:48:06 it has a neat instruction for doing a "microloop" where you loop over the instructions in a single machine word 13:48:21 that's pretty much the F18 13:48:32 modulo some strange little details here and there 13:48:34 i'm attracted by its bareness 13:48:47 spareness, rather 13:49:03 the code you write on those chips are all pretty much single threaded... just running on multiple machines 13:49:21 well sure 13:49:24 you don't have the locking problems you get with threads 13:49:32 i shouldn't put it in the same class as data-sharing threads 13:49:48 i have massive antipathy for data-sharing threads, some merited some some due to ignorance 13:50:05 but i also don't have good ability to think concurrently, i fear 13:50:16 but maybe i just haven't really tried 13:50:25 yeah.. just need practice probably :) 13:50:31 joe armstrong says sharing memory buffers is terribad and he's a cool guy so I say share data by communicating not the other way around 13:50:50 not that i'm any great expert but i don't see it as all that big of an obstacle either... 13:52:12 i made a shell where you guys can try mineswpr (minesweeper in retroforth): ssh to retro@argon.sabren.com ... password is currently 6dfigw5 13:53:10 RodgerTheGreat: haha awesome game idea. 13:55:32 tangentstorm: sweet, I'm in 13:55:52 I use a black-on-white terminal window so the greys are a little hard to see 13:56:02 i have programmed maybe one game in my life, and i've forgotten what it was 13:56:16 * avoscadeaux boring weirdoperson 13:56:53 when i was twelve or so and "learning c++" i got my kicks out of modifying an inventory / POS system from "Who's Afraid of C++ ?" 13:57:10 if only i were as good at programming now as i was then ! 13:57:16 avoscadeaux: I forget, have you heard about my "Forth Warrior" game? 13:58:00 tangentstorm: woah I just uncovered a bunch of cells and there's tons of shit on the stack 13:58:09 is that supposed to happen? 14:01:01 avoscadeaux: yes i have. i have the github link too \o/ 14:01:06 err 14:01:07 RodgerTheGreat: 14:01:24 cool 14:11:51 tangentstorm: I guess basically the question is if I actually made F18 Combat Simulator would you play it 14:12:02 this question goes for anyone 14:14:16 --- quit: sirdancealot1 (Ping timeout: 252 seconds) 14:19:46 i am terrible about following through on things, so i would say i would play it and then i would probably fail to 14:19:50 hone Forth Warrior imo 14:19:54 i'd be more likely to play that one 14:20:53 alright 14:21:04 I have had a few requests for a head-to-head competitive mode 14:21:19 it'll require some serious re-engineering but that ought to be worthwhile 14:24:47 --- join: ncv (~quassel@79.114.101.193) joined #forth 14:24:47 --- quit: ncv (Changing host) 14:24:47 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 14:27:28 --- quit: ncv_ (Ping timeout: 252 seconds) 14:27:31 --- join: sirdancealot1 (~sirdancea@98.82.broadband5.iol.cz) joined #forth 14:29:57 --- join: ncv_ (~quassel@79.114.107.71) joined #forth 14:32:25 --- quit: ncv (Ping timeout: 252 seconds) 14:35:15 --- quit: nighty^ (Ping timeout: 248 seconds) 14:35:25 --- join: nighty^ (~nighty@90.84.144.132) joined #forth 14:35:53 --- join: Onionnion (~ryan@adsl-68-254-167-191.dsl.milwwi.ameritech.net) joined #forth 14:39:57 --- join: ncv (~quassel@79.114.102.132) joined #forth 14:39:57 --- quit: ncv (Changing host) 14:39:57 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 14:40:15 --- join: kumool (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 14:42:35 --- quit: kumul (Ping timeout: 256 seconds) 14:43:25 --- quit: ncv_ (Ping timeout: 252 seconds) 14:51:44 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 14:54:29 --- quit: kumool (Ping timeout: 256 seconds) 15:16:47 --- join: kumool (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 15:18:59 --- quit: kumul (Ping timeout: 248 seconds) 15:21:45 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 15:24:19 --- quit: kumool (Ping timeout: 248 seconds) 15:56:29 --- quit: nighty^ (Read error: Connection reset by peer) 15:57:42 --- quit: kumul (Quit: Leaving) 16:03:21 --- quit: Tod-Work (Quit: Leaving) 17:30:46 --- join: zachk (~hask@unaffiliated/zachk) joined #forth 17:31:28 --- quit: JDat () 17:43:27 --- quit: beretta (Read error: Connection reset by peer) 17:44:36 --- join: beretta (~beretta@cpe-107-8-120-84.columbus.res.rr.com) joined #forth 17:46:14 --- join: beretta_ (~beretta@cpe-107-8-120-84.columbus.res.rr.com) joined #forth 17:49:22 --- quit: beretta (Ping timeout: 256 seconds) 17:59:46 --- quit: ncv (Ping timeout: 252 seconds) 18:35:51 --- quit: tgunr (Quit: Nity nite) 18:43:16 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 19:06:31 --- quit: RodgerTheGreat (Quit: RodgerTheGreat) 19:14:40 --- quit: karswell` (Read error: Operation timed out) 19:15:46 --- join: karswell` (~user@93-97-29-243.zone5.bethere.co.uk) joined #forth 19:17:26 --- join: kumool (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 19:20:03 --- quit: kumul (Ping timeout: 248 seconds) 20:15:30 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 20:16:02 --- join: mo (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 20:16:25 --- nick: mo -> Guest83787 20:18:37 --- quit: kumool (Ping timeout: 256 seconds) 20:19:47 --- quit: kumul (Ping timeout: 248 seconds) 20:30:09 --- join: I440r (~zhiming@197.sub-70-195-64.myvzw.com) joined #forth 20:30:09 --- mode: ChanServ set +o I440r 20:40:52 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 20:43:15 --- quit: Guest83787 (Ping timeout: 248 seconds) 21:02:06 --- join: kumool (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #forth 21:05:06 --- quit: kumul (Ping timeout: 248 seconds) 21:35:32 --- quit: Onionnion (Quit: Leaving) 21:55:01 --- join: kbmaniac__ (~dave@host86-157-24-246.range86-157.btcentralplus.com) joined #forth 21:55:01 --- quit: kbmaniac_ (Read error: Connection reset by peer) 22:17:05 --- quit: kumool (Quit: Leaving) 23:03:39 --- quit: bjorkintosh (Remote host closed the connection) 23:08:21 --- join: bjorkintosh (~bjork@ip68-13-229-200.ok.ok.cox.net) joined #forth 23:14:43 --- quit: I440r (Ping timeout: 248 seconds) 23:25:19 --- join: nighty- (~nighty@TOROON12-1279662182.sdsl.bell.ca) joined #forth 23:27:38 --- quit: nighty-_ (Ping timeout: 240 seconds) 23:28:47 --- quit: nighty- (Read error: Connection reset by peer) 23:29:09 --- join: mapour (mapour@linux.utu.fi) joined #forth 23:35:52 --- join: nighty- (~nighty@TOROON12-1279662182.sdsl.bell.ca) joined #forth 23:53:26 --- join: epicmonkey (~epicmonke@sabis.ru) joined #forth 23:55:23 --- join: protist (~protist@114.224.69.111.dynamic.snap.net.nz) joined #forth 23:59:59 --- log: ended forth/13.02.08