00:00:00 --- log: started forth/15.09.30 00:08:00 --- quit: ASau (Ping timeout: 240 seconds) 00:11:02 --- join: asagk (~asagk@i59F6D06E.versanet.de) joined #forth 00:14:57 --- join: darkf_ (~darkf___@unaffiliated/darkf) joined #forth 00:17:00 --- quit: darkf (Ping timeout: 240 seconds) 00:21:10 --- join: true-grue (~grue@176.14.218.33) joined #forth 00:21:25 --- join: smokeink (~smoke@221.7.213.34) joined #forth 00:46:07 --- join: Slaughtrec (~chatzilla@197.89.130.131) joined #forth 00:59:23 --- part: Slaughtrec left #forth 01:29:37 --- quit: smokeink (Read error: Connection reset by peer) 02:33:49 --- quit: karswell (Read error: Connection reset by peer) 02:35:02 --- join: karswell (~user@61.255.199.146.dyn.plus.net) joined #forth 02:40:41 --- join: aap (~aap@f055012019.adsl.alicedsl.de) joined #forth 02:42:16 hi, i want to implement a forth on the pdp-10 (simh) but i don't know how i should handle characters and bytes 02:42:28 i don't know what assumptions forth makes about how they work 02:42:58 pointer arithmetic on byte pointers is a pain on that machine e.g. 02:43:38 maybe someone can help me with figuring out how it should be done 02:51:54 Just make chars as wide as cells. 02:52:21 that seems so wasteful 02:52:38 First get something functional, you can optimize later. 02:53:57 i don't have much experience with forth, the question is what can you do with strings in forth? 02:54:13 is it assumed to you can just add and subtract one from an address? 02:54:21 to get to the next or previous character 02:54:22 There's a standard, read it. 02:57:34 you're right...only it's so large and is very abstract most of the time 02:58:19 You're wrong on both counts here. 03:00:50 forth standards certainly take time getting used to.. 03:07:53 well, i can't find much on strings in the standard 03:08:09 looks like they're pretty much implementation defined 03:45:56 --- nick: darkf_ -> darkf 03:46:12 --- quit: karswell (Read error: Connection reset by peer) 03:47:22 --- join: karswell (~user@61.255.199.146.dyn.plus.net) joined #forth 04:29:34 --- quit: TodPunk (Read error: Connection reset by peer) 04:29:56 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 04:35:06 --- quit: atommann (Ping timeout: 268 seconds) 04:38:57 --- quit: DGASAU (Read error: Connection reset by peer) 04:40:57 --- join: DGASAU (~user@194.31.92.26) joined #forth 04:48:33 --- quit: DGASAU (Read error: Connection reset by peer) 04:48:40 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 04:57:00 --- quit: mnemnion (Ping timeout: 240 seconds) 05:16:25 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 05:50:19 --- join: mnemnion (~mnemnion@107-0-228-218-ip-static.hfc.comcastbusiness.net) joined #forth 06:17:46 --- join: BitPuffin (~usefulPro@host217-41-32-21.in-addr.btopenworld.com) joined #forth 06:18:01 Does gforth not support any kind of paralellism? :( 06:18:19 how hard would it be to add words for native threads etc you think? 06:18:33 and like mutexes etc 06:19:58 Adding is not a problem, the problem is using all those. 06:27:23 DGASAU: hmm? 06:27:40 I guess what I'm worried about is things like dictionary memory etc 06:31:33 That's generic parallel programming, and it is hard. 06:38:50 DGASAU: well I'm not too worried about the fact that this type of concurrency is hard to program, I've done it before and with principles it can work, plus it's decent to use as a primitive for building more easy to use less shoot yourself in the foot stuff on top on 06:40:38 I'm more worried about being able to fully utilize all the CPU cores at a low level in forth 06:40:40 and if I can then great 06:41:13 just that I didn't see anything kind of native os thread support in gforth so I was worried that maybe it was super challenging to add or something 07:28:14 --- quit: proteusguy (Remote host closed the connection) 07:57:32 --- join: xyh (~xyh@183.54.163.82) joined #forth 09:03:01 --- quit: darkf (Quit: Leaving) 09:04:20 --- quit: asagk (Ping timeout: 240 seconds) 09:09:56 --- join: proteusguy (~proteusgu@ppp-110-168-229-114.revip5.asianet.co.th) joined #forth 09:09:56 --- mode: ChanServ set +v proteusguy 09:17:40 --- join: asagk (~asagk@i59F6DBDB.versanet.de) joined #forth 10:31:50 Hello, Forth people. I'm working on ForthFS http://hub.darcs.net/pointfree/ForthFS 10:32:28 pointfree: hmm interesting 10:38:47 ...and I wanted to ask, is there any sort of standard or convention on where source code BLOCKs are located on microcontrollers (for the sake of sane defaults)? Eventually I want this to work in a sourceless manner by writing transparently to the dictionary ( or something ) to save space on the uC...but for now I'm using Forth source code BLOCK(s) ( because I don't have my auto-pretty-printing yet http://www.lowfatcomputing.org/12/ 10:40:45 ( My formatting conventions are controversial anyway ) 10:55:12 --- join: beretta (~beretta@cpe-65-185-42-203.columbus.res.rr.com) joined #forth 11:26:20 --- quit: DGASAU (Ping timeout: 240 seconds) 12:03:51 --- quit: BitPuffin (Ping timeout: 244 seconds) 12:19:53 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 13:34:02 --- quit: xyh (Remote host closed the connection) 14:09:04 --- quit: mnemnion (Remote host closed the connection) 14:17:27 --- join: ASau (~user@46.114.105.25) joined #forth 14:38:46 --- join: kumul (~mool@adsl-64-237-236-48.prtc.net) joined #forth 14:53:32 --- join: Mat4 (~claude@ip5b40b95e.dynamic.kabel-deutschland.de) joined #forth 14:53:34 hello 14:54:35 hiya mat4 14:55:13 hi kumul 15:00:32 --- quit: true-grue (Ping timeout: 244 seconds) 15:09:06 --- quit: Zarutian (Quit: Zarutian) 15:25:45 --- quit: Mat4 (Quit: Leaving) 15:34:23 --- join: mnemnion (~mnemnion@2601:400:8001:14c9:30bd:71da:b008:fc43) joined #forth 15:47:45 --- quit: proteusguy_ (Ping timeout: 252 seconds) 15:48:00 --- quit: proteusguy (Ping timeout: 240 seconds) 16:00:49 --- join: proteusguy (~proteusgu@ppp-110-168-229-181.revip5.asianet.co.th) joined #forth 16:00:49 --- mode: ChanServ set +v proteusguy 16:00:55 --- quit: mnemnion (Remote host closed the connection) 16:01:06 --- join: proteusguy_ (~proteusgu@ppp-110-168-229-181.revip5.asianet.co.th) joined #forth 16:05:42 --- join: kumool (~mool@adsl-64-237-236-48.prtc.net) joined #forth 16:08:44 --- quit: kumul (Ping timeout: 244 seconds) 16:18:31 --- join: lynx` (~lynx@104.254.90.251) joined #forth 16:43:22 --- quit: aap (Ping timeout: 264 seconds) 16:53:16 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 16:53:22 --- quit: kumool (Quit: Leaving) 16:55:22 --- part: lynx` left #forth 17:33:27 --- quit: proteusguy (Ping timeout: 240 seconds) 17:36:38 --- quit: karswell (Read error: Connection reset by peer) 17:37:51 --- join: karswell (~user@61.255.199.146.dyn.plus.net) joined #forth 17:40:44 --- join: proteusguy (~proteusgu@ppp-110-168-229-181.revip5.asianet.co.th) joined #forth 17:40:44 --- mode: ChanServ set +v proteusguy 17:57:02 --- join: kumul (~mool@adsl-64-237-237-48.prtc.net) joined #forth 18:50:51 --- join: aap (~aap@x4db30d04.dyn.telefonica.de) joined #forth 21:43:02 --- quit: aap (Read error: Connection reset by peer) 21:52:32 --- quit: kumul (Read error: Connection reset by peer) 21:53:48 --- join: kumul (~mool@adsl-64-237-237-48.prtc.net) joined #forth 21:57:40 --- quit: asagk (Ping timeout: 240 seconds) 22:10:43 --- join: asagk (~asagk@i59F6DF53.versanet.de) joined #forth 22:31:08 --- join: aap (~aap@x4db4a3f9.dyn.telefonica.de) joined #forth 23:16:35 --- quit: karswell (Remote host closed the connection) 23:17:42 --- join: karswell (~user@61.255.199.146.dyn.plus.net) joined #forth 23:21:00 --- quit: kumul (Quit: Leaving) 23:44:26 --- join: xyh (~xyh@183.37.0.14) joined #forth 23:49:54 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 23:59:59 --- log: ended forth/15.09.30