00:00:00 --- log: started forth/02.10.16 00:02:21 --- quit: proteusguy (Read error: 110 (Connection timed out)) 01:03:13 --- quit: Robert ("ROBERT IN THE SKY WITH DIAMONDS") 01:06:02 --- join: Robert (~Robert@robost86.tsps1.freenet6.net) joined #forth 04:16:07 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 04:16:20 hi 04:28:24 hi 04:28:44 nah, do u already know what is that a! ? 04:34:01 no, damn !!!! dig web.... 04:35:04 oh, no need to 04:35:09 its simple 04:35:54 in colorforth (& in machine forth 4 the 1st time, ithink) there is a global variable 04:36:13 a so called register, named A, the Address reg 04:38:59 and what it is ? 04:39:22 i ran across it trying to port ColorForth IDE code 04:39:54 --- join: LuckyPhil (~phowlett@CPE-203-45-248-201.qld.bigpond.net.au) joined #forth 04:42:02 hi LuckyPhil 04:42:50 i started writing IDE drvr 4 Enth and flooded all around w/ lame questions, coz i could only read state/ say rezet 04:43:25 didn't have much luck huh? 04:44:02 i bump my head at porting IDE code from colorforth 04:44:33 dunno what damn thing 'a!' is, grepped src (color.asm) - fail 04:45:27 not sure either.. I thought it might be the address pointer. but I'm not sure 04:46:20 adress of what ? 04:47:20 of the A register.. not sure.. bit confusing I know 04:47:54 can i find Chuck's docs for his forth ? 04:48:42 should be on chucks page 04:49:41 colorforth.com ? damn minimal, no trace of doc 04:50:48 i don't think there is much doc at all.. except the asm source itself. chuck says that there isn't any doc yet 04:52:44 i grepped src for a! but failed 04:54:35 hmm... 04:54:43 perhaps its a macro 04:55:18 * Serg_Penguin can't run ColorForth, monitor doesnt hold 1024x7?? mode 04:56:02 damn, Chuck encrypted every damn thing w/ huffman, so no seaches... 04:56:25 a! is not in the enth color source 04:56:43 he knocked out 4too much 1 comlexity 04:58:11 --- part: LuckyPhil left #forth 05:09:08 --- quit: Serg_Penguin () 06:31:54 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 06:43:13 --- join: Herkamire (~jason@wsip68-15-54-54.ri.ri.cox.net) joined #forth 07:03:23 --- quit: Serg_Penguin () 08:14:35 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 08:31:46 --- quit: tathi ("bloody X...") 08:38:31 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 08:47:41 hi? 08:58:06 hello 08:58:28 you new to forth? 09:01:50 i know no forth 09:02:05 is forth used in bios? 09:02:10 in linuxbios/openbios? 09:02:14 OpenFirmware 09:02:43 openbios is the open-source OpenFirmware project? 09:03:37 isn't openbios open-source pc BIOS effort totally unrelated to openfirmware? 09:04:51 "OpenBIOS will be a free portable firmware implementation. The goal is to implement a 100% IEEE 1275-1994 compliant firmware." 09:05:13 i know no forth 09:05:21 OpenFirmware is the IEEE 1275 standards document 09:05:31 boltion_: what OS are you currently using? 09:05:33 whee, then I'm mistaken 09:06:28 linux 09:07:01 you could try installing gforth to play around with... 09:07:15 gforth is bletcherent 09:07:22 forth homepage? 09:07:37 enormous, primitives not in forth, spaghetti forth sources 09:08:21 XeF4: I know -- I don't have it installed on any of my machines 09:08:45 then why do you recommend it? ;-) 09:09:06 forth homepage? 09:09:12 a bunch of people here use it, at least enough to be able to help if anyone has problems... 09:09:50 bolt: there isn't an official one, http://www.colorforth.com/ (Moore's site) http://www.ultratechnology.com/ http://www.forth.org/ http://www.fig-uk.org/ 09:09:53 http://www.forth.org/compilers.html 09:09:55 all have useul info 09:13:58 gforth is a GNU program, so I'd assume it compiles without problems on a wide range of systems 09:14:11 what is forth used in most? 09:14:15 and it's certainly fine to play around with 09:14:41 it's just when you start getting into serious forth stuff and want to do stuff that you need to know how the internals work that it's really horrible 09:15:31 but its open 09:15:38 it shoudl be most accesible 09:15:51 boltion_: yeah, but it's huge and hard to read 09:16:11 bolt: many forths are "open", actually 09:16:18 what is forth used in most? 09:16:50 embedded systems, bootloading I suppose 09:18:30 one of the shipping companies' (UPS, I think) computers that the guys on the trucks have were written in forth 09:18:35 don't know if they still are... 09:21:14 ok, FedEx, not UPS. http://www.forth.com/Content/Stories/FedEx.htm 09:21:29 oh, and telescope controllers =) 09:22:59 well, of course :) 10:15:11 & house automation ;) 10:53:18 --- part: boltion_ left #forth 13:10:47 --- join: jacereda (~jacereda@VA1-1G-u-0007.mc.onolab.com) joined #forth 13:11:12 --- part: jacereda left #forth 13:11:45 --- join: jacereda (~jacereda@VA1-1G-u-0007.mc.onolab.com) joined #forth 13:12:10 hi 13:16:07 hi :) 13:16:24 Hi there. 13:16:56 --- join: Chef_ (~sam@m222.net81-65-249.noos.fr) joined #forth 13:40:05 --- quit: Chef_ ("Client Exiting") 13:57:39 --- part: jacereda left #forth 14:28:18 --- join: jacereda (~jacereda@va1-1g-u-0007.mc.onolab.com) joined #forth 14:50:52 w00000000000 15:03:37 hey Fractal :) 15:03:50 I can't get no satisfaction! 15:03:53 Hey man. What's up? 15:04:11 not much. you? 15:04:18 Not much. 15:04:29 wooooooo! 15:04:36 w00000000000000000000000000000000000! 15:04:39 Herk! Sup? 15:04:51 oh, not much. 15:04:55 ;) 15:04:55 Sounds fun., 15:06:26 --- quit: tathi ("blah...I'm going to go home and find something to eat...") 15:06:36 So, I made a wrapper "fgcc" for frugal, so you can compile to portable C code. 15:06:54 Should be useful for distributing forth programs to wider audiences. 15:07:43 interesting 15:08:10 Ya, it's okay. Apparently it's endian neutral now too, thanks to your patch. 15:08:31 --- quit: onetom (Remote closed the connection) 15:08:59 cool. I'll give it a try when I get home. (I'm leaving for there shortly) 15:09:32 Heh. Cool. Actually, fgcc hasn't been released yet. 15:09:41 Maybe... couple more days. 15:09:51 fooooooey 15:10:02 Well, if you like, I could release it now. 15:10:02 what's all this crap about releases ;) 15:10:27 do you use version control? 15:10:39 I dunno. I like to test a lot. 15:10:44 No, not yet. 15:10:54 Right now, it's only me working on it. 15:11:00 So no real need to. 15:11:17 I plan on bumping up to 1.0.0 soon, when I'll start it as a real project. 15:11:26 Which is what I do for most of my projects. 15:11:37 I use svn for all my programming projects. most of which are just me. 15:12:23 Cool. 15:12:27 svn? 15:12:41 Apparently it's better than CVS. I dunno. 15:13:30 --- join: onetom (~tom@novtan.bio.u-szeged.hu) joined #forth 15:14:08 http://subversion.tigris.org/ 15:14:40 Normally, I just have a file named "CHANGES", and backup often. :) 15:14:44 Works for me. 15:14:52 "The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community. 15:16:22 oops, I forgot. I'm not going right home. I'll won't be there for 4 hours. 15:16:28 my "version control" under *nix is usually just a 'backup' make target that makes a copy of the source tree in bak/ 15:16:57 if I were less lazy, I would diff against the previous backup orso 15:17:46 well, I'm off to my juggling club. later 15:17:48 --- quit: Herkamire ("leaving") 15:17:50 It's very rare for me to do something to the code that I can't easily undo. 16:46:32 --- join: tathi (~josh@ip68-9-68-50.ri.ri.cox.net) joined #forth 17:05:46 --- quit: jacereda (Read error: 110 (Connection timed out)) 17:41:47 --- join: Klaw (chuck@ip68-4-243-214.oc.oc.cox.net) joined #forth 19:22:04 --- join: tcn (tcn@tc3-login20.megatrondata.com) joined #forth 19:31:32 --- quit: tcn () 20:14:41 --- quit: Klaw () 20:24:02 --- quit: tathi ("leaving") 20:38:35 --- join: I440r (~mark4@1Cust60.tnt2.bloomington.in.da.uu.net) joined #forth 20:39:09 --- join: Herkamire (~jason@ip68-9-58-75.ri.ri.cox.net) joined #forth 20:54:51 --- quit: I440r ("Reality Strikes Again!") 21:10:32 --- quit: Herkamire ("leaving") 21:15:36 --- join: bugslayer (~thin@h68-146-166-145.cg.shawcable.net) joined #forth 21:18:04 --- nick: bugslayer -> thin 21:18:12 --- nick: thin -> futhin 21:19:13 --- nick: futhin -> bugslayer 21:24:24 --- part: bugslayer left #forth 23:59:59 --- log: ended forth/02.10.16