00:00:00 --- log: started forth/04.12.18 00:33:44 --- quit: Sonarman ("leaving") 00:59:54 --- quit: Herkamire ("bed") 01:23:03 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 05:18:39 --- join: Obakeneko (yumehito@giguz.turbo.nsk.su) joined #forth 05:38:24 --- quit: yumehito (Read error: 110 (Connection timed out)) 05:41:01 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 07:28:47 --- join: zoly (~l@ppp-82-135-5-206.mnet-online.de) joined #forth 07:29:00 g'day 07:30:20 hello 07:42:39 for the lovers of the perverse, there is now OOPS for bashforth 07:43:24 http://www.forthfreak.net/wiki/index.cgi?BashForth (last link, after the screen shot) 08:01:18 --- join: froop (~wossname@rn-v1w5a06.uwaterloo.ca) joined #forth 08:29:57 Wow 08:30:02 bashforth is incredible 08:30:45 It manages to take nearly a second on an 800Mhz G4 to execute "1 2 + ." 08:31:21 speed is indeed very platform dependant 08:31:32 cpu clock is not so much a factor 08:31:52 probably compiler quality for target platform is one 08:32:16 for example, speed diff between x86 and arm versions here is enormous 08:32:29 And the fact that Bash isn't exactly the fastest language in the world ;) 08:32:46 and indeed, the PPC based machines didn't perform so well yet 08:33:32 right. you wouldn't want to use bashforth for, say, real time video encoding :) 08:34:18 ID aren't using it to implement Doom 4 then? 08:34:35 "Bash isn't exactly the fastest language", ok, but that's not a platform specific issue 08:35:38 i was considering to add a compiler for ELF standalone code generation to bashforth 08:36:01 Why? 08:36:10 for the laugh 08:36:22 :) 08:36:57 this one, actually: http://www.forthfreak.net/wiki/index.cgi?NativeCodeCompiler 09:47:15 --- quit: warpzero ("Lost terminal") 09:47:33 --- join: warpzero (~warpzero@wza.us) joined #forth 10:14:54 --- quit: tathi ("leaving") 10:19:34 --- part: zoly left #forth 10:40:35 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 10:41:48 --- quit: saon ("Leaving") 11:14:17 hi Herkamire 11:23:27 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 11:23:42 RetroForth/Native 7.x works quite well under Bochs now :) 11:24:22 * crc yawns. I should take a Saturday off work once in a while. 11:36:36 --- join: Sonarman (~snofs@adsl-64-169-92-226.dsl.snfc21.pacbell.net) joined #forth 11:50:20 hi crc :) 11:50:30 very cool. does it come with a config file for bochs? 11:53:43 nice :) 11:55:26 yes 11:55:34 * crc is going to get a pizza; bbs 12:10:28 back 12:14:38 crc: what version of bochs do you use? any special requirements? 12:15:50 I'm using Bochs 2.1.1, for Linux, with the "X" display option 12:16:12 does it have to have a serial port? 12:16:17 No 12:16:33 ok. at first it was paniking or something about the serial port 12:16:37 The code is compiled into the image, but not used if you don't call the words 12:16:52 ok cool. I'll try turning serial off in the config 12:16:54 Try changing the "com1:" to /dev/ttyS0 or something if you want serial port support 12:18:14 In 7.6-beta2 (which I'm working on), I'll be adding in my block editor, and the latest bochsrc.txt that I'm using here 12:18:54 I don't have a serial port 12:19:04 ok 12:19:09 just disable it then :) 12:19:12 I tried mapping it to a pty 12:19:19 then it got further and crashed 12:19:30 :) 12:19:57 It *might* also work with qemu 12:20:03 I haven't tried it though 12:38:21 --- quit: tathi ("booting herkforth") 13:00:02 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 13:15:03 --- quit: madgarden ("*frotz*") 13:42:09 --- quit: tathi ("work") 13:57:24 --- quit: OrngeTide ("buh") 15:06:59 --- quit: qFox (Read error: 54 (Connection reset by peer)) 15:24:19 --- join: kuvos (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 15:24:22 --- quit: kuvos (Client Quit) 15:31:39 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 15:46:50 --- join: ows (~ows@83.132.99.46) joined #forth 15:50:00 --- quit: Sonarman (Read error: 60 (Operation timed out)) 16:20:59 --- join: robert (~purple@c-4d5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 16:39:00 --- quit: qFox (Read error: 104 (Connection reset by peer)) 16:51:33 --- join: snowrichard (rsnow@207-254-202-217.dialup.mar.shreve.net) joined #forth 16:51:38 Hi 16:51:42 hello 16:51:53 I am at my mom's on her XP machine 16:52:17 Cool 16:52:37 * robert is spending his christmas vacation in front of his computer 16:53:01 I am on a permanent vacation 16:53:34 A lot of time for computing then :) 16:53:47 I went to that web site and looked at that ARM system. 16:53:56 Haven't done that yet 16:54:01 Does it look any good? 16:54:03 its tiny 16:54:24 in size 16:54:25 I was looking at the Altair article on wikipedia 16:54:59 one of my uncles is a TI engineer. his name is on the patent for thier first calculator. he has an Altair that the built in his living room 16:55:14 he built 16:55:57 Jerry Merryman (well he is my dad's uncle) 16:56:47 Very neat 16:57:06 I have old memories of my dad's old calculator...really early model 16:57:26 Was still using it until a few years ago 16:57:40 When will people learn that old computers aren't useless? :) 16:57:43 I used a slide rule in high school. scientific calcs weren't around yet 16:58:43 or PC's for that matter 16:59:08 my first computer was a KIM-1 16:59:43 Never heard of it..when was it made? 16:59:53 1976 17:00:07 a single board trainer basically 17:00:23 we added 8K of ram that cost us about 300 17:00:58 yes that was a K 17:01:05 8K is a lot 17:01:22 8192 bytes 17:01:29 Right 17:01:46 Thousands of instructions, and still some room for data 17:02:01 we fit our assembler/editor in there 17:02:15 the final version was 2.2K 17:02:22 Not bad 17:02:32 Did it have any video output? 17:02:49 we had a glass tty, but I preferred the paper one :) 17:03:13 no video on board just serial output 17:03:28 for a teletype 17:03:59 I got an old dot matrix printer I was thinking about using for something like that 17:04:17 Should try to get some PS/2 connectors so that I can connect a keyboard, too. 17:04:46 you can get the schematics for that system I used on the internet. there are people that have build thier own. Why I don't know ;} 17:05:47 Which CPU did you use? 17:05:55 is was a 6502 17:05:55 I'd prefer to use something I already have. 17:05:58 OK 17:06:07 Got some z80s and various microcontrollers 17:06:53 there was a book once called "threaded interpreted languages" by Byte Books where they designed a Z80 Forth 17:07:47 need to go check on my son 17:07:54 be back in a bit 17:07:54 OK, see you 17:13:18 I'm back 17:13:29 Hi again 17:15:42 --- quit: snowrichard () 17:39:41 --- join: Telebyte (1000@pD9E101FC.dip.t-dialin.net) joined #forth 17:40:26 Hallo 17:40:51 hi 17:41:49 just reading Brodie's Starting Forth 17:42:24 can you recommend a free system so I can follow the examples? 17:42:31 Linux/x86 17:49:30 Hmm... 17:49:35 Which standard does it follow? 17:49:59 I'm using isForth for Linux on x86, but it's not exactly the same Forth variant. 17:50:09 There's also gforth. 17:50:34 the author mentions ansi, but the book is from 1981 17:50:49 Hehe 17:51:01 it is just for basic examples anyway - I'm a total noob 17:51:05 If I were you, I'd go for some Forth and just learn the differences. 17:51:14 I think most basic things will work in isForth. 17:51:18 isforth.clss.net 17:51:25 And gforth, hrm...google. 17:51:37 ok, thanks 17:57:45 --- mode: ChanServ set +l 83 17:58:13 --- join: Sonarman_ (~snofs@adsl-64-171-254-225.dsl.snfc21.pacbell.net) joined #forth 17:58:45 --- nick: Sonarman_ -> Sonarman 18:00:45 --- quit: Telebyte ("leaving") 18:02:44 Hi Sonarman 18:11:27 hi robert 18:19:38 * robert does the forth dance 19:03:17 --- join: arke (apache@11.198.216.81.dre.siw.siwnet.net) joined #forth 19:04:27 Hi 19:04:40 --- quit: arke (Client Quit) 19:27:49 --- join: arke (apache@11.198.216.81.dre.siw.siwnet.net) joined #forth 19:31:39 hrm. 19:31:43 you know what I just thought of 19:32:02 you can implement a complete record system in Forth in maybe half a block 19:32:28 Record system? 19:32:37 yeah 19:32:37 Like...a database? 19:32:40 like C structures 19:32:45 like C structures 19:32:48 :) 19:32:48 Oh 19:32:54 and unions too, simply layered on top. 19:33:02 sooo simple 19:33:03 man 19:33:04 Yes.. I'll see what implementation I use in tforth 19:33:22 the way gforth does it is so complex compared to this. 19:33:22 4 lines 19:33:37 robert: lets see is 19:33:42 : struct: create 0 , here 2- 0 does> @ create allot ; 19:33:42 : bitem over + swap create , does> @ + ; 19:33:42 : witem 2* bitem ; 19:33:42 : ;struct swap ! ; 19:34:54 yeah 19:35:01 thats exactly how I imagined it :) 19:35:14 except that you can add more data types and transparent unions etc. 19:35:16 I think I stole that from isForth 19:35:22 Don't remember who Mark stole it from 19:38:43 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 19:39:33 Hi 19:40:12 : STRUC CREATE HERE 0 , 0 DOES> @ ; 19:40:13 hi rob 19:40:22 hi tathi :) 19:40:33 : WORDITEM CREATE DUP , 2 DOES> @ ; 19:40:39 hey arke 19:40:40 : BYTEITEM CREATE DUP , 1 DOES> C@ ; 19:40:44 : ENDSTRUC SWAP ! ; 19:40:45 doing structures in forth? 19:40:58 tathi: just an idea. 19:41:20 in fact, I came up with it and its the same way many other people seem to do it. 19:41:25 unions should be simple too :) 19:41:39 yeah 19:41:57 Good if you want named structures on a machine with 4kB in RAM. 19:42:40 i dont like the idea of named structures like that. 19:42:47 If I'm gonna do something like it, I'll just do 19:42:56 : offset create , does> @ ; 19:43:37 and theres a plus sign between @ and ; 19:44:30 Real forthers have a good memory and know how to use + 20:02:58 real forthers know the address of their data 20:03:16 Exactly. 20:03:48 real forthers don't even fetch from that address, they just assume the most likely value 20:04:14 One step too far, remembering the address is realistic 20:04:32 PEEK 43827 20:05:44 Hrm. 20:06:01 I should resume that stupid Forth project. 20:06:13 512b limit. 20:06:51 Perhaps I could accept 1kB... perhaps. 20:07:36 <3? 20:07:38 people in Bangledesh don't have ANY bytes, and you're going to waste yours?!? 20:07:49 Bangladesh 20:07:51 Of course not. 20:08:32 f0rtH r3v0lutionary f0rc3s 20:09:06 Armed with forty forth flags, and a pig. 20:09:57 Forth traditionalism can be seen as a memory exercise. 20:10:08 "Oh, you'll learn to remember the block numbers" 20:13:54 Time to try to sleep a little, I guess. Night 20:25:37 --- join: Sonarman_ (~snofs@adsl-64-169-93-3.dsl.snfc21.pacbell.net) joined #forth 20:36:06 --- quit: Sonarman (Read error: 110 (Connection timed out)) 20:37:49 --- quit: Sonarman_ ("leaving") 21:12:45 --- quit: arke ("CGI:IRC") 21:28:46 --- join: arke (apache@11.198.216.81.dre.siw.siwnet.net) joined #forth 21:34:05 --- quit: arke ("CGI:IRC") 22:03:26 --- quit: tathi ("leaving") 22:24:28 --- quit: fridge ("rock out with your cock out") 22:29:26 --- join: Sonarman (~snofs@adsl-63-196-0-194.dsl.snfc21.pacbell.net) joined #forth 22:47:52 --- part: ows left #forth 23:59:59 --- log: ended forth/04.12.18