00:00:00 --- log: started retro/09.03.15 01:10:22 --- quit: virl (Remote closed the connection) 07:59:14 --- join: jenspall (n=jenspall@194-144-99-20.du.xdsl.is) joined #retro 08:01:16 Has anyone made any progress in implementing networking in/for retroforth? 08:30:54 <_crc_> No networking in the current codebase. IIRC, there was a few network apps written for 9.x though. 08:32:54 <_crc_> I remember helping thin work on an irc client and a simple telnet-like thing for plaing MUDs with. 08:34:55 <_crc_> There has been a little discussion of adding some form of networking to the ngaro vm, but I don't know if anyone has actually begun work on it yet. 09:04:13 Yes, I saw some discussion about this in the forums (using ports above 12 for instance) 09:04:50 I am toying with the idea of giving this a shot 09:06:49 It would be very nice and very powerful (IMO) to be able to run several processes, each running a retroforth image, and having some way for the to talk over the network 09:15:54 <_crc_> Please feel free to do so. I'd love to see multiple instances of retro communicating. 09:17:34 Do you have any thoughts/preferences on how you would like to see this implemented, that is, how would you like to use it? 09:18:55 For my part, I need to implement a server able to accept multiple connections and a client able to connect to at least one location 09:29:55 <_crc_> I have no preferences in this. 09:29:55 For the server, one port might written to to configure the listening IP address (or name) and network port, and then some other port might return the port number an incoming connection has been connected to. 09:39:00 I might throw together a document describing what I'm thinking, just to have something more concrete to discuss. 09:40:04 have to go - talk to you later 09:49:35 --- quit: jenspall (Read error: 60 (Operation timed out)) 11:23:52 --- quit: erider (Read error: 104 (Connection reset by peer)) 11:25:38 --- join: erider (n=erider@pool-173-69-149-163.bltmmd.fios.verizon.net) joined #retro 11:33:04 --- join: erider__ (n=erider@pool-173-69-149-163.bltmmd.fios.verizon.net) joined #retro 11:49:55 --- quit: erider (Read error: 110 (Connection timed out)) 13:05:43 --- join: crc (n=charlesc@c-68-80-139-0.hsd1.pa.comcast.net) joined #retro 13:39:21 --- join: GitHub1 (n=GitHub1@129.177.74.65.static.xc88.engineyard.com) joined #retro 13:39:21 retro10: 3Charles Childers 07master0 SHA1-39ff7af 13:39:21 updated image conversion tools 13:39:21 http://bit.ly/vK4eK 13:40:19 --- quit: GitHub1 (Read error: 104 (Connection reset by peer)) 13:48:45 --- join: jenspall (n=jenspall@194-144-99-20.du.xdsl.is) joined #retro 14:33:08 --- join: SimonRC (n=sc@fof.durge.org) joined #retro 14:34:36 ooh, this place is still here 14:34:57 it's been here for years 14:35:27 oh, wait, I was thinking of a different one 14:35:31 never quite dead, though it's been really quiet the last two years or so 14:36:02 (now, which is that forth whose once-active web forums almost stop in 2005?) 14:36:59 retro's board died out in mid-2007, so it must be a different one 14:37:59 could have been 2007 14:39:02 'tis the curse of Forth: it is so easy to implement there are 1001 variants, most of them no good outside of a tiny audience and not very great inside it. 14:40:00 2006 was when I took a break from actively working on retro for personal reasons (health, job changes, other priorities); I started work again slowly in 2008 and have gradually rewritten things until January, when I finished the core code for the 10.0 release 14:40:03 yup 14:40:54 ah, ok 14:41:23 (work on the 9.x release pretty much ceased when Quartus finished writing a complete ANS layer over it, proving that the 9.x codebase was mature enough for pretty much anything; at least for me) 14:42:12 colorForth is beter than most: it is still not very good outside of its intended audience (CHM), but AIUI it is exdcellent with that audience. 14:44:18 that's because the audience is one man (chuck) working on one main app (okad) 14:45:35 yup 14:45:51 retro 10 is more experimental, closer to the 7.x/8.x retro implementations, which were simpler and easier to work on/expand 14:46:37 I enjoy the freedom to change things more; a living/evolving environment is nice to play and work with 14:47:09 I have so much by CHM and Jeff Fox and Ray that claiming a significant degree of ANSI compatibility puts me off a Forth 14:47:20 *I have read 14:47:26 ;-) 14:48:10 I have a partial compliance layer, but it's not forced, and seldom is updated 14:48:31 just enough to provide another tool for porting over small pieces of ANSI code if I need to 14:49:01 (it's also not shipped with the core retro distribution) 14:50:19 ok 15:03:19 --- join: virl (n=virl__@chello062178085149.1.12.vie.surfer.at) joined #retro 15:32:38 --- quit: jenspall (Read error: 60 (Operation timed out)) 17:05:44 --- quit: crc (Read error: 104 (Connection reset by peer)) 17:32:53 * SimonRC goes to bed. 23:59:59 --- log: ended retro/09.03.15