00:00:00 --- log: started forth/07.08.01 01:02:28 --- quit: Baughn (anthony.freenode.net irc.freenode.net) 01:02:28 --- quit: mem4tim (anthony.freenode.net irc.freenode.net) 01:02:44 --- join: mem4tim (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 01:02:44 --- join: Baughn (n=svein@2002:54ca:ec08:0:0:0:0:1) joined #forth 01:37:55 --- join: gihgi (n=irc@bzq-88-155-128-198.red.bezeqint.net) joined #forth 01:54:54 --- join: nighty^ (n=nighty@221x249x65x78.ap221.ftth.ucom.ne.jp) joined #forth 02:11:09 --- quit: JasonWoof ("off to bed") 02:32:35 --- quit: slava () 02:33:13 --- quit: nighty^ ("Disappears in a puff of smoke") 03:45:12 --- quit: madwork (Read error: 110 (Connection timed out)) 04:58:48 --- quit: gihgi ("[BX] If idiots could fly, IRC would be an airport") 05:40:44 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 05:53:39 --- join: nighty^ (n=nighty@p2136-adsau16honb13-acca.tokyo.ocn.ne.jp) joined #forth 06:46:17 --- join: ghjghjg (n=jghjghjg@p5B077A9B.dip.t-dialin.net) joined #forth 06:48:19 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 06:48:45 --- quit: ghjghjg ("Verlassend") 07:31:45 --- join: edrx (i=edrx@201.5.12.36) joined #forth 07:33:29 --- join: Al2O3 (n=Al2O3@75.39.59.142) joined #forth 08:26:14 --- join: madwork (n=foo@204.138.110.15) joined #forth 10:12:16 --- join: forther (n=forther@12.36.112.3) joined #forth 10:13:36 --- quit: forther (Client Quit) 10:49:12 --- join: tetonca (n=chris@66.155.140.245) joined #forth 10:49:45 --- join: JasonWoof (n=jason@c-24-63-217-45.hsd1.ma.comcast.net) joined #forth 10:49:45 --- mode: ChanServ set +o JasonWoof 10:59:17 --- quit: Al2O3 () 11:00:40 --- join: Sieur_de_Bienvil (n=cuss@user-11202fq.dsl.mindspring.com) joined #forth 11:00:45 Hello. 11:02:05 hi 11:12:38 --- join: sgx___ (n=sgx@r200-125-42-81-dialup.adsl.anteldata.net.uy) joined #forth 11:17:54 --- quit: edrx (Read error: 110 (Connection timed out)) 11:22:01 hi. all. is it forth/os an operating system? From Where can I download a release/or distribution? thank sin advance 11:22:59 This question is hard to answer. 11:23:03 Forth is a programming language. 11:23:14 But it has been implemented as a hardware-native OS. 11:23:21 There are no distributions of Forth-based OSes. 11:24:33 ah! ok 11:24:35 thanks 11:27:22 forth is a concept not an implementation. ;) 11:27:35 There's hundreds of the latter but (arguably) only one of the former. 11:28:02 sgx___ I'm having good luck with ciforth. 11:28:05 recommend it. 11:29:21 look at [ http://home.hccnet.nl/a.w.m.van.der.horst/forthimpl.html ]. 11:29:54 One version of it can be written as the OS directly to media. 11:30:08 The linux version works fine without glibc present. 11:30:36 (a consideration if you're running Firmware Linux which is uClib, not glibc, based). 11:32:27 tetonca. thanks. i'm reading but, but that means that forth has to run over a linux linux kernel? 11:32:44 sgx: optional. your choice. 11:33:26 Linux will provide access to hardware you might not have drivers for in a more generic installation of Forth (stand-alone). 11:34:41 The ciforth I run can run any Linux command from inside Forth. Ex. 'S" ./do.sh" SYSTEM'. 11:34:41 aha 11:35:15 Seeing color-ls run from inside forth is an experience you might enjoy. 11:35:47 For an OS that runs on the bare hardware Native Oberon is also worth a look. 11:36:57 See [ http://www.oberon.ethz.ch/ ]. 11:37:17 * kc5tja LOVES Oberon. 11:37:45 Really. Neat. I like booting Oberon on the laptop when I need a word processor in 30 seconds and it's powered off. To jot down ideas. 11:37:57 It is unfortunate that few projects are written in Oberon. 11:38:18 I haven't seen a Forth for oberon .. would the metaphors work? 11:38:25 Alas, nobody will use it because it's totally foreign territory for open-source contributors. 11:38:54 Metaphors? 11:38:54 thanks. i'm playing now with lina... 11:39:22 kc5tja: (from wa1tnr) I mean the fact that Oberon isn't a CLI like many/most Forths are. 11:41:02 Well, if you're implementing a pure ANSI Forth, I doubt it'd be easy to implement, since Oberon is a pure event-driven architecture, while Forth assumes a sequential process model. 11:41:14 It's doable, but it gets really hairy really quick. 11:41:37 It's better to just write a Forth which has a new user interface, but which implements as many of the ANS words as you can, and ditch the rest. 11:41:52 But, you'll also need to constrain the runtime environment too. 11:42:13 Forth grants total access to its memory space, but Oberon is incompatible with this (due to objects being "managed" by the garbage collector). 11:42:23 kc5tja: I was thinking more along the lines of using the terminal emulation in Oberon to talk to a forth. 11:42:28 So you'll need to make sure that @ and ! and friends are constrained. 11:42:37 Which would of course break the Oberon 'metaphor' as I call it. 11:42:53 I just don't understand what you mean then. 11:43:08 Are you saying to talk to a Forth system on another machine? 11:43:14 Well in Oberon to do something you mouse-click. In forth you type . 11:43:29 Unless your Oberon program was written with a CLI interface. 11:43:39 I don't know what I'm saying. I'm trying to think of how these two great technologies could interact. 11:43:54 I think you're over-thinking it. :) 11:44:08 AmigaOS was a combined GUI/CLI environment, and you just wrote your code to use one or both models. 11:46:44 sgx: I've found a shell script with './lina -s ./myforth.fs' compiles nicely to a forth you can extend by invoking it directly. 'lina -s ./myforth.fs' is same as typing commands inside lina (including '"myforth" SAVE-SYSTEM'). 11:47:47 (.frt isn't recognized by vim' syntax highlighting and .fs isn't complained about in lina). 11:48:49 gforth is possibly more useable generally but requires glibc present. 11:49:30 isforth??? :) 11:49:38 isforth doesnt use glib or any OTHER lib 11:49:48 cool. where is it? 11:49:53 but isforth isnt ans 11:49:55 isforth.clss.net 11:50:01 I don't care about ans that much. 11:50:12 tnx. 11:50:48 I've seen this. 11:50:57 u have seen isforth? 11:51:02 Sure. 11:51:20 Seems to me he had something going I needed -- maybe on a microcontroller. 11:51:21 was it insufficient for your needs? 11:51:29 8051? 11:51:35 yeah 8051 indeed. 11:51:47 I wanted it on C8051F120 ;) 11:51:51 he == me... you used my 8051 assembler??? :) 11:51:58 oooohhh 11:52:12 I think you were onto that at some pt. hi. 11:52:12 is that a cygnal 8051? 11:52:17 Yes it is. 11:52:38 I run AMRForth for C8051F330 presently. That's gforth-based. 11:52:41 yes. ive written two 8051 forths for cygnal processors but they werent complete 11:53:00 yea i was writing a native arm forth for the nintendo ds too 11:53:09 So that's why I've seen it. The web page style is distinct enough (color scheme) that I recognized it immediately just now. 11:53:18 purple :P 11:53:31 Hehe. I almost wrote you at some pt. 11:53:40 if i could write an assemblers other than 8051 i'd be set 11:53:50 i need an x86 assembler AND an arm assembler 11:54:21 I'll definitely look into your repository to see what you've been up to. 11:54:32 sigh. not much 11:54:47 i wrote a debugger tho and some code for a specific I/O board 11:54:49 I'm not up to your skill level anyway but I can sometimes fit someone else's work to my needs. 11:54:50 --- join: Al2O3 (n=Al2O3@adsl-75-30-131-92.dsl.rcsntx.sbcglobal.net) joined #forth 11:55:09 i basiclly ported the c code drivers for it so its horrible code 11:55:09 The F120 is a monster of an 8051. 11:55:13 yes 11:55:40 I have the target board but it's paperweight since I aquired it. I won't run silabs tools with it. I have them tho. ;) 11:56:23 i developed a forth compiler for the 120 i believe, i wanted it to interface with isforth but i never got that far 11:56:35 Charley at AMR is supposed to be sending me an AMRForth port for the F120 but haven't heard from him in a while. 11:56:48 I think Wolfgang Allinger has F120 going with AMRF. 11:57:41 i ported isforth to dos 16 bits and wrote a serial term app to talk to my 8051 forth 11:57:49 cool! 11:57:59 What 8051 do you run your forth on? 11:58:01 i have the cygnal (si labs) target board 11:58:18 erm i THINK i did one for the 120 lol 11:58:23 wow. 11:58:28 i did two but they were done like 3 or 4 years ago 11:58:40 I have a JTAG-programmed F330 I use to initialize other F330's with. ;) 11:58:42 i never released the dos version of isforth 11:59:03 its coded using eric isaacsons a386 assembler 11:59:29 with the a386 macro language i can assemble a entire forth kernel with threadded vocabularies 11:59:32 HASHED 11:59:52 Cheater ;-) 11:59:53 im particularly proud of those macros lol... 12:00:03 So publish or the secret dies with you. ;) 12:00:28 cant do that with nasm, isforth has to go thru each vocab on launch and RE hash them all. i.e. all words are "assembled" onto the first chain of a vocab 12:00:42 do you have a386/d386? 12:00:59 its the 386+ version of a86 12:01:08 I haven't done anything with those, so I don't know how to answer. 12:01:24 Are those old-school assemblers? 12:01:25 which i think is the best assembler ever created (equal to devpac for the amiga ) 12:01:49 * kc5tja never liked devpac. I always prefered a68k+ and blink. 12:02:11 i like the way devpac could do 12:02:20 label code comment 12:02:26 with no ; to start the comment 12:02:39 anything after valid label/code on a line is automatically treated as a comment 12:03:21 All the assembler I know I wrote inside AMRForth for F3xx series (silabs). 12:03:58 ok, lunch, bbl 12:04:11 rgr. nice to meet u. 12:07:39 * kc5tja cannot stand NOT using ; to initiate a comment. 12:07:40 :) 12:08:09 Too many times I've had cases where I've accidentally entered wrong code, and the assembler thought half of my instruction was a comment. 12:08:31 Not so much a problem on the 6502/65816, but on the 68000, it can be a pain. 12:08:32 heh. /me afk a bit. 12:08:47 * kc5tja will be here....plodding along with Java... 12:08:57 Although I'll get to lunch myself in about 30 to 40 minutes or so. 12:22:03 back. 12:43:20 --- quit: Al2O3 () 12:55:47 --- join: Al2O3 (n=Al2O3@adsl-75-30-131-92.dsl.rcsntx.sbcglobal.net) joined #forth 12:58:00 --- quit: sgx___ ("Abandonando") 13:22:58 --- join: slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 13:22:58 --- mode: ChanServ set +o slava 13:28:46 --- quit: timlarson_ ("Leaving") 13:44:29 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-134-188.pools.arcor-ip.net) joined #forth 13:46:09 --- quit: Snoopy42 (Nick collision from services.) 13:46:33 --- nick: snoopy_1711 -> Snoopy42 14:06:00 has anyone here been at a euroforth? 14:07:05 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 14:07:40 hey. 14:08:33 hi. 14:09:05 This is getting to be a bit like BBSing in the final days. All the users were also sysops. 14:09:15 ?? 14:11:01 in the sense of "every forth programmer also has written at least one forth himself"? 14:11:52 quote: no unix system admin can truly call themselves a real unix sys admin until they had configured sendmail at least once. and nobody in their right mind would want to do it twice 14:12:03 how can you call yourself a forth coder if you never created your own forth :) 14:12:28 hm. oh well. may i still be here? 14:12:51 i'm looking for a forth running on microcore natively. maybe i need to create that myself. :) 14:12:56 ;) 14:12:56 :) 14:13:16 I was just suprised at the high S/N ratio. 14:13:21 your here soaking in the rays of forthness in prep for creating your own masterpiece :) 14:14:26 * H4ns is a little afraid that he'll never be able to return to the software industry once that happened. 14:15:07 I4: any magic words needed besides 'fsave ' in isforth? 14:15:08 in here? 14:15:31 its always been my personal policy to NOT dictate to you what you may or may not chat about in here 14:16:48 H4ns: You don't *have* to want to create your own forth to hang out here, but if you stay you may find yourself wanting to create one "just because". 14:17:46 It's probably the only way to understand forth in depth. 14:18:54 hm. i might instead ask my son to create his own forth. but then he'll propably never be able to get a "normal" computer related job when he comes to the age. 14:19:14 You can *use* Forth without writing your own, but if you have the least bit of interest in compilers or such FORTH makes it so easy to poke around. 14:19:20 anyway. hopefull i'll find some time to work on maisforth on the weekend, i'll then pester you again. 14:19:46 (first i need to convince xilinx' data2mem to not crash anymore, though :/ ) 14:21:03 Who wants a normal job? 14:21:34 creating a new forth is good if it will fill some new niche 14:21:52 but creating yet another 80% implementation of half of ANS forth is a waste of time, IMHO 14:21:56 amforth met that goal nicely. 14:22:19 having an interactive environment on a $3 DIL chip is teh rox 14:22:36 slava if it is done as a learning experience 14:22:47 but what is there to learn? 14:23:02 forth 14:23:14 you can learn forth without implementing it form scratch 14:23:18 by writing applications and libraries 14:23:32 Nah, you learn about compilation, not FORTH. 14:23:34 isforth is cool, don't get me wrong 14:24:29 Do as slava says and write apps and/or libraries if you want to learn FORTH. 14:25:29 i don't want to learn forth for the sake of it. i use it for hardware control, and i need a small self-hosted forth for an fpga project i am doing. 14:26:11 In that case the folks here can probably help. 14:27:56 yeah, you guys already helped. i'm happy to be your user! bye for now. 14:28:06 see you. 14:32:37 I'll add my two cents to that; you don't learn Forth by building a Forth. 14:34:26 i learned more about forth by creating isforth than in the whole of the time i was using it 14:34:33 the language i mean 14:35:12 i've noticed factor contributors who write real code often have better insight into how the language should evolve than i do 14:35:15 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 14:36:52 I think Factor has the benefit of being a single codebase. 14:37:07 Forth has so many implementations that this doesn't occur. 14:37:21 So instead of contributing back to the Forth implementation, people just invent their own Forths. 14:37:30 yeah, that's a bit of a pity. 16:42:44 --- log: started forth/07.08.01 16:42:44 --- join: clog (n=nef@bespin.org) joined #forth 16:42:44 --- topic: 'Welcome to #forth. We discuss the Forth programming language and a variety of technical subjects. Introduction and Helpful Reading: http://forthfreak.net/index.cgi?FnFC | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | Gforth compiler: http://tinyurl.com/s8uho | http://quartus.net/search | Paste: http://forth.pastebin.ca | http://angg.twu.net/miniforth-article.html <- due soon. Suggestions? 8-|' 16:42:44 --- topic: set by edrx on [Thu Jul 12 17:04:11 2007] 16:42:44 --- names: list (clog Sieur_de_Bienvil @Quartus @crc wossname crest_ @tathi neceve Quartus__ Snoopy42 @slava @JasonWoof madwork nighty^ Baughn mem4tim gnomon uiuiu H4ns kc5tja slava32 cmeme segher timlarson mrsbrisby ccfg @I440r TreyB tris tlockney warpzero maht madgarden uiuiuiu) 16:43:51 I suppose 'it depends' is not an adequate answer :) 16:44:14 Have you heard of the 3-instruction Forth system? 16:44:17 In broadest terms, the host has some mechanism for executing code in the target 16:44:17 * kc5tja tries to dig a URL 16:44:31 No, I haven't. 16:44:58 http://pygmy.utoh.org/3ins4th.html -- this might be helpful. But also others might have other ideas too. Quartus has more experience than I do in this area. :) 16:45:09 This seems to fulfill what Quartus was saying though. 16:45:10 Thank you very much. 16:46:49 Oooh! Cool! 16:48:43 This just what I needed! Thanks again! 16:49:39 No problems. 16:49:53 this page actually was the original inspiration for my Kestrel-1's IPL circuitry. :D 16:50:29 Alas, I couldn't get it to support bidirectional data flow for some retarded reason (it had something to do with the PC's parallel port), so I couldn't use it for debugging purposes. 16:55:42 That's a shame. 17:00:22 I like this: 17:00:22 Had we but memory enough and time, 17:00:22 this wastefulness, Programmer, were no crime. 17:00:22 The embedded system box is a private place and fine, 17:00:22 but none should there, I think, megabyte ROMs enshrine. 17:01:06 Somebody with a Wordsworth fetish and too much time on his hands? :) 17:01:25 lol 17:45:36 --- quit: Sieur_de_Bienvil (Read error: 110 (Connection timed out)) 18:35:27 --- quit: tathi ("leaving") 19:10:11 --- join: edrx (i=edrx@200.217.105.25) joined #forth 19:33:19 --- join: Sieur_de_Bienvil (n=cuss@user-1120nmr.dsl.mindspring.com) joined #forth 19:35:14 --- join: tetonca (n=chris@66.155.140.215) joined #forth 19:35:24 Hello again. 19:46:20 Hello. 20:15:19 --- join: ziggurat (n=ziggurat@95.fa.3845.static.theplanet.com) joined #forth 20:48:00 --- quit: wossname () 21:20:52 --- part: Sieur_de_Bienvil left #forth 22:05:44 --- quit: ziggurat ("Leaving") 22:32:02 --- quit: tetonca ("User disconnected") 22:44:16 --- quit: edrx (Read error: 113 (No route to host)) 23:59:59 --- log: ended forth/07.08.01