00:00:00 --- log: started forth/06.02.11 00:52:42 --- join: jungledog (n=jungledo@adsl-64-217-181-151.dsl.lgvwtx.swbell.net) joined #forth 00:52:56 --- part: jungledog left #forth 01:38:19 --- join: I440r (n=foo@24.242.160.169) joined #forth 01:39:01 morning I440r 01:47:43 hi 01:47:53 hey how ya been? 01:49:42 at a bar watching the GORGEOUS barmaids DANCE on teh bar haha 01:49:56 seriuosly? 01:50:02 i video'd it with my camera fone 01:50:12 no you cant see lol 01:50:15 there is no polite way to respond 01:50:23 enjoy. 01:50:28 (found one) 01:50:29 im gona cut a CD and give it to one of them 01:50:36 a cd of what? 01:50:45 of her dancing on the bar lol 01:50:48 ah 01:51:23 problem is the videos are in 3g2 format and the only converters ive found are either NOT free or do NOT WORK 01:51:35 write yer own 01:51:44 no thanx lo 01:51:46 lol 01:51:48 heh 01:51:54 slacker 01:56:43 hey I440r can you field a question while you leer? :) 01:56:49 sure 01:56:52 heh 01:57:01 roll your tongue back into your head :)! 01:57:03 ok umm 01:57:13 in your forth-busy-ness 01:57:30 do you have a running forth-based system on linux? 01:57:42 yes. isforth 01:57:50 but im not in linux atm 01:58:00 right, ... 01:58:33 have you extended isforth beyond a new build yet? 01:58:53 no, been looking for work and now i need to find a new apartment too 01:59:11 not even over the years since you first developed isforth? 01:59:39 oh ive done lots of releases over time bit not recently 01:59:54 ok, well that's good 02:00:23 but what i'm asking about is `incorporation of tools for productivity' - stuff to actually do stuff 02:00:49 such as ? 02:01:03 like regular expression tools for instance; a file browser 02:01:16 (off the top of my head) 02:01:28 how about an assembler and metacompiler first lol 02:01:57 they are top of my list but the assembler HAS to be able to take the existing souces AS IS (or with a few spaces injected) or i wont use it 02:02:01 it's far and well past time for those, i wanna be doing stuff with a forth-bsed thing 02:02:09 * already 02:02:36 isforth is useable. you could create the file browser with little problem 02:03:08 i gtg zzz its 4 am here 02:03:13 nite 02:03:20 er i THINK its 4 am 02:03:22 let me check 02:03:54 yup 02:03:56 nite :) 03:22:56 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 03:25:25 http://acarol.woz.org/ 04:49:06 --- quit: virl ("Verlassend") 04:50:18 --- join: PoppaVic (n=pete@0-2pool236-56.nas22.chicago4.il.us.da.qwest.net) joined #forth 06:29:34 --- quit: madgarden ("?OUT OF DATA ERROR") 06:30:45 --- join: madgarden (n=madgarde@Toronto-HSE-ppp3713137.sympatico.ca) joined #forth 06:48:48 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 07:47:40 --- join: venandocarvarow (n=venandoc@h062040252008.plc.cm.kabsi.at) joined #forth 08:17:49 --- quit: PoppaVic ("Pulls the pin...") 08:19:19 --- join: PoppaVic (n=pete@0-2pool238-40.nas24.chicago4.il.us.da.qwest.net) joined #forth 08:44:06 --- quit: madgarden ("?OUT OF DATA ERROR") 08:47:47 --- join: madgarden (n=madgarde@Toronto-HSE-ppp3713137.sympatico.ca) joined #forth 09:03:45 --- quit: PoppaVic ("Pulls the pin...") 09:08:19 --- join: jungledog (n=jungledo@adsl-64-217-181-151.dsl.lgvwtx.swbell.net) joined #forth 09:25:08 --- part: jungledog left #forth 09:49:02 --- quit: madgarden ("?OUT OF DATA ERROR") 10:06:25 --- join: madgarden (n=madgarde@Toronto-HSE-ppp3713137.sympatico.ca) joined #forth 10:17:36 --- quit: venandocarvarow (Remote closed the connection) 10:18:07 --- quit: madgarden ("?OUT OF DATA ERROR") 10:19:34 --- join: madgarden (n=madgarde@Toronto-HSE-ppp3713137.sympatico.ca) joined #forth 11:00:06 --- quit: tathi ("leaving") 11:25:26 --- join: ThinkingInBinary (n=tom@pool-68-163-171-142.bos.east.verizon.net) joined #forth 11:25:54 Quartus: I have a PIC, now I need various sundries such as hookup wire, a voltage regulator, and a programming adapter. 11:32:45 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 11:32:45 --- mode: ChanServ set +o JasonWoof 11:32:59 --- quit: ThinkingInBinary (Nick collision from services.) 11:33:11 --- join: ThinkingInBinary (n=tom@pool-68-163-135-152.bos.east.verizon.net) joined #forth 11:33:49 Sorry, dog + loose phone cord + DSL = badness. 11:34:09 Hi ThinkingInBinary. Sounds like progress. 11:41:21 Quartus: Yeah, it should be good. 11:41:54 Quartus: I know it's insane, but I want to get 4 or 8 of these (or maybe the newer 16-bit ones) and write an implementation of MPI (or something similar) for them so I can have a cluster in my pocket. 11:45:45 That would rock. 11:47:52 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 11:49:41 Quartus: Have you ever done any sort of cluster/multithreaded programming? 11:53:25 Hi ThinkingInBinary. Yes, a bit. 11:54:54 Application-specific work. I'm not too excited about the amount or configuration of technology that fits in a given pocket, I'm more of a pragmatist; use or build the system that's required for the task at hand. 11:58:00 Gotta go. 11:58:07 There's no task BTW, it's just tech for the sake of tech. 11:58:10 --- quit: ThinkingInBinary (Remote closed the connection) 11:59:05 In which case just fill your pocket with CPUs. 11:59:25 :) 11:59:51 Well, I'm serious -- if they don't have a purpose, they don't need an OS; they don't even need power or an interface. 12:00:28 They don't even need to be CPUs, just the *idea* of CPUs. Maybe not even that. And I bet you can fit a lot of that in a pocket. :) 12:00:33 I know. I just like the way you always come out and say stuff like that. :) 12:00:52 :) 13:23:09 --- join: virl (n=virl@62.178.85.149) joined #forth 13:32:06 --- quit: uiuiuiu (Remote closed the connection) 13:32:10 --- join: uiuiuiu (i=ian@dslb-084-057-248-231.pools.arcor-ip.net) joined #forth 14:16:57 --- quit: tathi ("leaving") 14:24:02 --- join: crc (i=crc@pool-70-110-157-48.phil.east.verizon.net) joined #forth 14:37:57 --- quit: Raystm2 ("Raystm2 has decided to ignore the entire internet, so sorry you had to he there.") 14:45:03 --- join: Raystm2 (n=Raystm2@adsl-69-149-41-128.dsl.rcsntx.swbell.net) joined #forth 14:51:03 --- quit: Cheery ("Leaving") 14:52:29 --- quit: Raystm2 (Read error: 104 (Connection reset by peer)) 14:55:36 --- join: Raystm2 (n=Raystm2@adsl-69-149-41-128.dsl.rcsntx.swbell.net) joined #forth 15:51:21 --- quit: I440r () 15:59:01 --- nick: Quiznos -> Bueller 16:01:20 --- nick: Bueller -> PurpleSmurf 16:14:59 --- join: sproingie (n=chuck@64-121-2-59.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 16:26:58 --- quit: sproingie (Remote closed the connection) 16:29:35 --- nick: PurpleSmurf -> Quiznos 17:00:18 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-135-058.pools.arcor-ip.net) joined #forth 17:03:31 --- join: ThinkingInBinary (n=tom@pool-68-163-135-152.bos.east.verizon.net) joined #forth 17:03:54 Quartus: hey 17:05:21 Quartus: you around? 17:07:42 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 17:07:53 --- nick: snoopy_1711 -> Snoopy42 17:10:06 Hey. 17:10:44 Quartus: Have you worked with PIC's before? 17:11:00 Yes, but never where I had to build the system from the ground up. 17:11:27 Quartus: What did you use as a programmer, and do you know of an easy one to build? 17:11:47 Wow. Ancient history, whatever I came up with. No, I have no advice on anything current. 17:18:08 there are millions of web pages about building simple in-circuit PIC programming thingies 17:18:48 segher: I know, I just found the one I remembered (Broccoli18) 17:21:28 segher: Is there a well-supported Linux one that is relatively standard? I don't want to be taking a shot in the dark picking a programmer to build. 17:22:18 most are just "send some shit over a serial or parallel port", so i imagine all of those work just fine from linux 17:22:34 i don't have any hands-on experience with any, sorry\ 17:22:40 segher: okay, thanks 17:22:52 sorry i can't help 17:23:17 Yeah, they're simple gadgets. 17:23:44 Quartus: I just don't wanna build some random design if there's a specific one that's good. 17:23:56 What are you building this for, again? 17:24:34 Quartus: my little FORTH computer gizmo. I'm not going to start straight into that--I'm going to build the usual LED blinker (=~ Hello, world! for PICs) first--but I need a programmer. 17:24:56 I mean, what's the Forth gizmo for? 17:25:17 Quartus: Just 'cause I can, for now. I'll see if there's a good use for it later. 17:25:29 Quartus: FORTH makes a good RPN calculator, for one. 17:25:37 Quartus: And I'll try to give it some simple PDA functionality. 17:26:00 Battery life is the biggest issue with portable devices. 17:26:17 Quartus: Yeah, the PIC I got has really low power consumption. 17:26:31 Quartus: I'm going to be using the internal 8 MHz oscillator, and probably leaving it in sleep mode when there's no input. 17:27:11 Quartus: Just a sec, I'm checking the voltage range it supports. 17:31:01 Quartus: It's 4.2 to 5.5 volts, so... I could run it off of 3 AAA batteries (maybe 4 AAA's plus a voltage regulator?) 17:31:41 Quartus: There's a low-voltage version that can go down to 2.0 volts, but I don't have it. 17:32:31 3 AAA, eh? Or maybe one rechargeable. 17:32:45 Um, you mean like a nonstandard rechargeable battery? 17:32:55 Like a "5 volt cell" or something like that? 17:33:03 Nonstandard? Not an A series, anyway. But there are dozens of standard rechargeables. 17:33:10 Ok. 17:33:19 Or I could do 4 NiMH AAA's? 17:33:37 I guess. 17:35:56 Do you know how much power is in an average battery? 17:36:19 Google'll have the specs on AAAs, I'm sure. 17:48:05 1.2..1.6V, don't drain much more than 1W 17:50:23 It appears AAA's have ~1125 mAh worth of power. 17:51:59 And it appears that the *maximum* power used by the uC (with all inputs simultaneously sinking and sourcing full voltage and current--physically impossible) is 1.0 W. 17:52:13 depends a lot on the exact cells, but yes that's a rough estimate 17:52:43 so that's 4 hrs max for your 4-cell thing 17:53:11 closer to 2.5hrs in real life 17:53:38 segher: It will be in sleep mode most of the time though. 17:53:48 segher: I'm checking the data sheet, just a sec. 18:00:04 segher: At 4 MHz (using the internal oscillator), the max current for the CPU itself is 8 mA when running, 4 mA when idle, and 0.015 mA when sleeping. 18:00:49 segher: At 40 MHz, it's 75 mA running, 35 mA idle. 18:01:49 segher: In a special secondary oscillator mode (where it uses an oscillator input normally used for a timer) at 32.768 kHz, it gets 0.180 mA running and 0.052 idle. 18:02:01 segher: Those are all maximums, and the sleep current is the same for all because the oscillator is off in sleep mode. 18:02:18 segher: I should make a power budget for this so I can see what kind of battery life to expect. 18:06:45 segher: And you can change the internal oscillator's speed in powers of 2 from 32 kHz to 32 MHz. 18:13:05 So maybe 3 hours of actual use. 18:13:17 Maybe a month of total standby. 18:14:43 Quartus: Wait, 1125 mAh / 8 mA = 140 hours of use at 4 MHz. 18:14:56 Quartus: I'm about to extrapolate for all speeds, 32 kHz to 32 MHz. 18:15:04 At 4 MHz it'll only seem like 140 hours. :) 18:15:41 And you have to drive a display device. 18:16:49 And an amplifier if you want any sound output. 18:17:49 Quartus: Sound? Probably not yet. 18:17:56 Quartus: Display I can look up in a sec. 18:17:58 An occasional beep might be nice. 18:18:02 Quartus: true. 18:18:28 Plus you'll want to power an input device of some kind. 18:20:14 Quartus: Buttons, for a chording keyboard. 18:20:47 Quartus: If I play my cards right I can have it unpowered most of the time and only power it up for a short time every 10ms or something like that using a atimer. 18:20:51 s/atimer/a timer/; 18:21:03 ThinkingInBinary, battery life isn't gonna matter for this collection of parts, it'll never leave the breadboard :) 18:21:10 Quartus: :-b 18:21:28 Quartus: It's worth a shot. 18:22:08 Is it? Ground already covered by the original Palm Pilot. 18:22:16 Quartus: Dammit, this chip is so new they don't have a lot of the power characteristics I'd like to know. 18:22:21 Quartus: Like I said, :-b 18:23:04 Quartus: I have a cell phone that does all this and 1000x more. I have a TI-89 calculator that does too. And an old (broken) CLIE. 18:23:09 Quartus: But I didn't build any of them. 18:24:06 Yes, but as I said before you left, I build to a need, not just to build. 18:24:24 Quartus: I have a need to build gadgets. 18:24:27 Quartus: How's that? ;-) 18:24:42 Quartus: It's like when people say "getting there is half the fun". 18:25:07 Thing is, if you're never going to do anything with the resulting gadget, battery life doesn't matter; leave it out. Also leave out the CPU and the screen and the keyboard. 18:25:19 Quartus: But then I can't do anything with it at all. 18:25:31 Quartus: I mean battery life could be sacrificed, but not all I/O. 18:25:34 So you get to the final state with zero effort expended. Ideal engineering. 18:26:07 Quartus: Poof. 18:27:29 Quartus: I dunno, I guess I see it the same way people see that putting Linux on their toaster is cool. I want to put FORTH on a small gadget I can program. 18:27:36 Quartus: It's fun. 18:28:00 Ok. I suspect you'll lack focus if you're not working toward a target. 18:28:28 Quartus: I have a pretty good idea of what I want out of it, even if I don't have an application. 18:30:25 Quartus: I want insanely good battery life, an LCD and chording keyboard (the LCD can be backlit but I won't count it when figuring battery life), and probably ANS compliant FORTH. I'd like it to have enough performance that it's not laggy when being used interactively, and isn't ridiculously slow (I'll come up with a benchmark target once it runs FORTH, and then optimize it.) I'd like to eventually add external storage. 18:31:00 Quartus: It also needs a handful of blinky LED's for the heck of it (pulse-width modulated to save power), and a rechargeable battery would be cool. 18:31:46 Quartus: I'd like to start out programming it by giving it simple watch/organizer/PDA functions. (Clock/calendar source is something I haven't considered yet.) 18:32:31 Quartus: Version 2.0 will have 4 PIC's communicating over a local bus (probably Controller Area Network) and running some sort of message passing system. Not sure yet how to synchronize program code between them. 18:32:50 Quartus: Maybe more or less than 4. Version 1.5 might have a 16-bit PIC if they come out soon enough. 18:33:07 Quartus: Somewhere after this version I'd also like to add a graphic LCD, and maybe a touchscreen. 18:33:16 Quartus: Is that a good target? ;-) 18:33:39 Quartus: (if not a little overambitious) 18:35:21 Quartus: ? 18:35:45 ThinkingInBinary, I'm the wrong guy to ask. 4 times the CPU is 4 times the battery and 4 times the heat dissipation. 18:36:16 If you need a machine to write Forth on because there's something you actually want to do, the machines exist, and in quantity. 18:36:57 Quartus: Heat dissipation is not a problem at 40 MHz max. I don't expect good battery life out of the multiprocessor version anyway. 18:36:57 Complete with sophisticated input devices, good screens, decent battery life, etc. 18:37:10 Quartus: I dunno, I guess I just want to build one for fun. 18:37:48 Ok. But I don't see that it presents particularly interesting challenges, and the result is something that effectively already exists, so it's just a reinvention of the wheel. 18:38:04 As a pragmatist I'd encourage you to do something new, that needs doing. 18:45:51 Hmm. 19:01:03 Quartus: Jeez, Microchip wasn't kidding when they said these things were low-power. 0.5 microwatt typical sleep current. 19:02:59 That's low. 19:03:03 Quartus: Yeah. 19:03:56 Quartus: Whoops, that's microamps. 19:04:27 Quartus: At 32 kHz, you get 0.1 mA run current, 0.018 mA idle current, 0.0005 mA sleep current. 19:04:47 Quartus: At 4 MHz, 4 mA run, 1.8 idle, same sleep (no oscillator in sleep mode anyway) 19:05:11 Pl/ 19:05:13 oops 19:05:13 Ok. 19:07:21 Assuming no parts but the LCD and CPU, *with* the backlight on and the CPU running full throttle at 8 MHz (that's a bit of an oxymoron, isn't it?) I still get 8 hours typical and 4 hours minimum battery life. 19:08:06 Assuming 10% run and 90% idle (not sleep), and assuming 10% backlight use, I get 34 hours min and 65 hours typical. 19:08:23 Not bad. 19:09:10 Quartus: Whoops, those figures were for *one* AAA battery. 19:09:18 Quartus: I need 3 or 4 to get the right voltage, so let's try 4. 19:10:10 Quartus: ;-) over 1 day with backlight on and full speed. 19:10:34 Quartus: Over 1 week assuming 10% run and 10% backlight on. 19:10:38 Quartus: brb 19:10:54 With no peripherals? Memory? Screen? 19:11:19 Oh, I see you factored in an LCD of some kind. 19:11:56 Quartus: Yeah, a 2x16 character LCD from CrystalFontz.com. 19:12:01 Tiny. 19:12:06 Quartus: Yeah. 19:12:18 Quartus: They have 128x64 graphic LCD's, lemme check the specs on those. 19:12:24 Ok. Well, lest I pour too much cold water on, let me tell you I'll never get excited about this hardware project. 19:12:30 Quartus: I can tell. 19:12:48 Quartus: Just for my own curiosity, what would it take to catch your interest? 19:12:58 Doing something new. 19:13:05 Quartus: Like? 19:13:16 I'm not the Oracle at Delphi, ThinkingInBinary. :) 19:13:23 Quartus: lol 19:14:24 Not a simple NIH reaction to existing hardware. 19:14:44 Quartus: Should I add some buzzwords? Would it help if it was AJAX-powered, and understood RSS feeds? <-- joke ;-) 19:15:17 ok, you clowns are driving me nuts -- we need an Acme Forth (does linux too) 19:15:20 :) 19:15:34 Quiznos: Acme Forth? 19:15:49 yea, Wiley's source for productivity 19:15:52 :) 19:16:04 Quiznos: ? 19:16:29 if you dont know Americana, then i'm out of your league of language :) 19:16:34 or 19:16:39 It's Wile E. Coyote. 19:16:41 i'm speaking a foreign language 19:16:44 that too, Q 19:16:46 :> 19:16:56 Quiznos: OHH! 19:16:58 Quiznos: lol 19:17:06 :) bingo 19:17:18 Quiznos: ACME, I get it now. 19:17:22 heh 19:17:26 slow on the uptake? 19:17:31 19:17:53 Quiznos: yeah, reading CPU datasheets can do that to you. 19:18:44 i did that during the 80s 19:20:50 * ThinkingInBinary wonders if it would be feasible to build a cluster of 16 small microcontrollers like PIC's and get decent performance out of it. 19:20:54 i trademark Acme Forth!1 19:20:57 it's mine! 19:20:58 :)~ 19:21:52 Quiznos: Ok. 19:22:01 :) lol 19:22:07 lighten up :) 19:22:09 a nm? 19:22:42 Quiznos: parse error at line 3 "a nm?" 19:22:49 nanom 19:23:05 Quiznos: nanometer? 19:23:15 yea 19:24:23 Quiznos: I don't get it. 19:24:29 lol 19:24:29 ok 19:24:54 people say "lighten up a little", i said, a nanometer 19:25:03 but i'm just funin ya :) 19:25:15 Quiznos: Ah. 19:25:33 Quiznos: /me is really slow on the uptake tonight. 19:26:39 so go sleep 19:27:18 Quiznos: But I don't *wanna* sleep! /me whines. 19:27:33 it's goodly to sleep. 19:27:52 Quiznos: Yes, and I can do it later. 19:28:51 Quartus: What if I made it able to do realtime 3D raytracing on a graphic display? Would that be interesting enough? 19:31:49 Quartus: Surprisingly enough, the smallest graphic LCD (which is 122x32 pixels, 5.2x1.5 cm viewable--quite tiny) actually uses less current. 19:34:24 Quartus: What about one of these? http://www.crystalfontz.com/products/12864c/ 19:38:08 Quiznos: Those look pretty cool, they're ~3x5 cm 128x64 pixel graphic LCD's with built-in analog touchscreens. 19:38:20 cool 19:40:11 Quiznos: Yeah, they seem cool. They're $36-42, depending on connector. 19:40:24 that's not expensive 19:40:29 i'm going to bed. 19:40:30 nite 19:40:31 --- join: Invifer4 (i=WINNT@12-208-98-237.client.insightBB.com) joined #forth 19:41:11 Quiznos: okay, nite. 19:49:06 Quartus: You still around? 19:58:04 Yes. 19:58:35 Realtime 3D isn't exactly new territory, even for low-end hardware. 20:02:26 --- join: I440r (n=foo@rrcs-24-242-160-169.sw.biz.rr.com) joined #forth 20:02:51 Quartus: I give up. 20:03:19 Quartus: There's nothing new I can do. 20:06:53 Quartus: How about if I interface it to a light controller for drama tech stuff? 20:07:02 ThinkingInBinary, it's not up to me. 20:08:09 I can't imagine needing a PIC to control stage lighting; I'd use a regular-size computer. But if it's for your own purposes, go nuts. 20:11:12 --- join: segher_ (n=segher@dslb-084-056-131-194.pools.arcor-ip.net) joined #forth 20:13:12 --- quit: neceve ("Bye people, I'm leaving") 20:13:38 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 20:14:38 --- join: llama32 (n=zak@087.a.001.beg.iprimus.net.au) joined #forth 20:14:48 what's a tiny forth interpreter? 20:14:55 like tiny as in as small as possible 20:15:44 Couple of K maybe. 20:16:08 Establishing a VM takes about 500 bytes of code. 20:16:12 know of one? 20:16:32 What platform? What capabilities? 20:20:39 Quartus: How about a robot? 20:22:02 i want something very simple (to build upon and play with, not for production), in C that will run on linux, not needed to conform to any standards, just the very basics 20:22:24 llama32: There's gforth, I think it's in C, it does run on Linux, but it's not very small at all. 20:23:11 --- quit: segher (Read error: 110 (Connection timed out)) 20:33:54 No, it's huge. Hmm. There's a Standard Forth called pforth ,but it's not miniature. There was an IOCCC entry a couple of years ago that was a tiny Forth engine. 20:34:07 ThinkingInBinary, don't choose your projects based on what I find interesting. 20:38:12 Quartus: lol 20:38:27 Quartus: Is it stupid to do a project just because it's a personally interesting challenge? 20:39:18 Quartus: Even if it's already been done by others? 20:39:20 You need me to answer that? :) 20:40:04 Quartus: Guess not... :-\ 20:40:33 I'm just saying I'm not enthused about a project to build a second-rate PDA. There's undoubtedly a hardware-hackers channel somewhere on freenode full of people who would light right up about it, though. 20:41:35 Quartus: ##microcontrollers, probably. 20:42:04 Maybe. 20:42:07 llama32: graspForth is in C, about 22k compiled 20:42:11 llama32: ftp://ftp.taygeta.com/pub/Forth/Compilers/native/misc/graspForth/ 20:44:51 I also know of SIF (http://takethis.org/sif), but don't know the compiled size offhand 20:45:03 TILE is an oldie that isn't large. 20:45:11 UNTIL is supposed to interface with C. 20:45:53 * crc recalls UNTIL being a pain to compile; but it has been years since I touched that 20:46:16 ATLAST is also written in C, about 80k compiled, but that can be trimmed down pretty easily 20:47:05 I remember an antique called cforth. 20:47:27 cforth needs some modifications to build on modern Linux systems 20:48:55 http://daishi.dhservers.net/~crcone/dev/asau/c-forth/ 20:48:58 I believe that. 20:49:06 has an updated version on it 20:59:46 Quartus: I'm going to bed now, see you later. 21:00:06 --- quit: ThinkingInBinary (Remote closed the connection) 21:25:38 --- quit: I440r () 23:39:22 --- quit: llama32 (Read error: 110 (Connection timed out)) 23:59:59 --- log: ended forth/06.02.11