00:00:00 --- log: started forth/08.02.21 00:22:17 --- quit: nighty^ ("Disappears in a puff of smoke") 01:12:28 --- quit: sauvin (Read error: 110 (Connection timed out)) 01:19:46 --- join: cr1 (n=crc@70.20.222.220) joined #forth 01:20:26 --- quit: crc (Read error: 101 (Network is unreachable)) 02:25:19 --- quit: timlarson (Read error: 104 (Connection reset by peer)) 02:25:35 --- join: timlarson__ (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 02:52:18 --- join: nighty^ (n=nighty@p3047-adsau16honb13-acca.tokyo.ocn.ne.jp) joined #forth 06:16:04 --- quit: nighty^ ("Disappears in a puff of smoke") 07:36:12 --- join: edrx (i=edrx@189.25.14.62) joined #forth 08:17:32 --- quit: ramkrsna_ ("Leaving") 08:32:51 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 08:53:27 --- quit: forther ("Leaving") 08:55:26 --- join: foxchip (n=fox@166.129.179.113) joined #forth 09:02:37 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 09:52:22 --- part: edrx left #forth 10:07:38 --- join: Quartus__ (n=Quartus_@205.205.178.5) joined #forth 10:10:09 --- join: Quartus___ (n=Quartus_@205.205.178.5) joined #forth 10:18:04 --- join: arke (n=arke@p57A76885.dip.t-dialin.net) joined #forth 10:18:04 --- mode: ChanServ set +o arke 10:19:15 --- join: edrx (i=edrx@189.25.14.62) joined #forth 10:36:22 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 11:01:26 --- join: ygrek (i=user@gateway/tor/x-f33276d8b7aad2fc) joined #forth 11:18:43 --- join: viric (n=viric@81.184.47.142.dyn.user.ono.com) joined #forth 11:18:47 Hello! 11:19:08 I'm trying to write some forth files, and run them with gforth. 11:22:31 --- part: edrx left #forth 11:24:01 3 cheers for viric! 11:24:03 can I make a, let's say, Linux binary from forth code? 11:24:14 not with gforth 11:24:31 though you can mark the file as executable, and put this at the top: #! /usr/bin/gforth 11:24:41 then it'll be executable like shell scripts 11:24:45 ah ok 11:24:48 but people will still need gforth installed to run it 11:24:56 (the space after #! is important) 11:25:00 Maybe there is another program to do that? 11:25:09 some forths support this 11:25:13 iirc gforth does not 11:25:15 Ah, gforth must parse that #! too, yes. 11:25:21 right 11:25:26 #! is a comment word in gforth 11:25:34 good. 11:25:46 mmm 11:25:58 Can you point me to some program, not for embedded systems, written in forth? 11:26:02 if you're just getting started I'd recommend worrying about binaries later 11:26:33 oh, I suck at this game. I always write everything from scratch 11:26:33 In fact the script may run quite fast, I guess. 11:26:47 :) 11:26:57 yeah, gforth is quite fast for an interpreted language 11:27:02 quite fast indeed 11:27:08 Looking for 'forth' in google, or in freshmeat, point me only to forth compilers 11:27:17 points. 11:27:25 guess you could take a look at my CGI stuff: http://jasonwoof.org/gforthcgi 11:27:54 Oh, I was trying to write a cgi in fact. 11:28:46 shiver me timbers! 11:29:34 I don't know enough English to understand that. :) 11:30:17 just a weird way to say I'm a little suprised 11:30:26 something that pirates supposedly say 11:30:52 I'll come in some minutes... We have a 'building meeting' with the neighbours. 11:31:06 thank you! It's great that I can find forth-people in irc :) 11:31:06 http://www.youtube.com/watch?v=fqMu6e5Dgtg 11:31:26 yeah, sometimes we take a couple hours to respond, but we've got a good group here 11:49:52 --- quit: foxchip (Read error: 110 (Connection timed out)) 12:38:55 --- quit: ygrek (Remote closed the connection) 12:39:38 --- join: ygrek (i=user@gateway/tor/x-6aa3b5a2da6f8001) joined #forth 12:41:39 --- join: forther (n=forther@207.47.34.100.static.nextweb.net) joined #forth 13:20:58 --- join: snoopy_1711 (i=snoopy_1@dslb-084-059-099-150.pools.arcor-ip.net) joined #forth 13:28:02 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 13:28:13 --- nick: snoopy_1711 -> Snoopy42 13:57:43 Is it possible to link 'forth' code to C, so it can be called from C? 14:01:28 What kind of 'forth' code, viric? 14:01:36 viric: It depends on the Forth environment. Ficl ( http://ficl.sf.net/ ) is designed to be embedded into a C application, so you can both call C from Forth as well as call Forth from C. 14:02:29 I have a C-based forth interpreter embedded in my application, and we can run forth words. 14:03:25 On the other hand, if you want to use a forth that generates native code, it will also need to export a C-callable entry point (matching the C ABI for the target platform). 14:04:40 I like FICL, and I even did the "port" to BeOS many years ago. My current project uses pForth, mostly for the license. 14:08:18 I took a look at pForth when I was choosing a Forth environment to embed into my application. I went with Ficl for some reason, though I cannot remember why at the moment. It might have had to do with the need to pause and resume the VM now that I think about it. 14:08:53 "Pause and resume"? 14:10:52 My host app is an ancient (20 year old) 68k Mac app written in Pascal. I needed a way to have the Forth environment block on i/o from the host app. In Ficl, I implemented a "PAUSE" word that throws a special exception. I catch this exception in the Ficl interpreter and return to the host app. Later, the host app resumes the execution of the Ficl interpreter exactly where it left off using a "continue" operation that I added to the VM. 14:11:59 I may have tried to do this in pForth and ran into issues. Or maybe I had compilation issues with pForth (and my early-nineties C compiler). Or perhaps I just didn't try hard enough to make pForth work. I started this project years ago and don't exactly remember why I went with Ficl over pForth. 14:22:37 --- quit: ygrek (Remote closed the connection) 14:30:21 hmmm interesting! Thank you! 14:35:28 malyn: Hmmm. Given the *current* version of pForth (which you might not have had access to), I don't see any reason you couldn't do it. A special VM primitive that bailed out of the execute loop with the stacks intact (and perhaps a resume flag in the "execute token" entry point) would do it. 14:37:44 Briefly glancing over the pForth docs again, it doesn't seem like anything that I am doing would preclude me from solving the problem in pForth. I'll have to see if I can dig around and figure out why it is that I abandoned pForth. On the other hand, my app is working in Ficl, so this may be one of those "let the past be the past" kind of things. 14:38:24 Sure, I wouldn't change just for the heck of it. 14:45:17 time to sleep... thanks! 14:45:20 --- quit: viric ("Leaving") 14:49:24 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 14:49:24 --- mode: ChanServ set +o tathi 14:54:00 --- nick: cr1 -> crc 14:54:07 --- mode: ChanServ set +o crc 15:00:59 --- join: crest__ (n=crest@p5B106B34.dip.t-dialin.net) joined #forth 15:04:07 --- join: malyn_ (n=malyn@unaffiliated/malyn) joined #forth 15:05:42 --- quit: crest__ (kornbluth.freenode.net irc.freenode.net) 15:05:43 --- quit: crest_ (kornbluth.freenode.net irc.freenode.net) 15:05:43 --- quit: lucca (kornbluth.freenode.net irc.freenode.net) 15:05:43 --- quit: maht (kornbluth.freenode.net irc.freenode.net) 15:05:44 --- quit: malyn (kornbluth.freenode.net irc.freenode.net) 15:05:44 --- quit: slava (kornbluth.freenode.net irc.freenode.net) 15:07:48 --- join: slava (n=slava@li13-154.members.linode.com) joined #forth 15:08:09 --- nick: malyn_ -> malyn 15:11:17 --- join: maht (n=maht@85.189.31.174.proweb.managedbroadband.co.uk) joined #forth 15:11:19 --- join: crest__ (n=crest@p5B106B34.dip.t-dialin.net) joined #forth 15:12:30 TreyB: Do you15:16:38 --- join: crest_ (n=crest@p5B104F01.dip.t-dialin.net) joined #forth 15:16:38 --- join: lucca (n=lucca@kuu.accela.net) joined #forth 15:17:18 --- quit: crest_ (Connection timed out) 15:19:32 --- quit: lucca (kornbluth.freenode.net irc.freenode.net) 15:20:00 --- join: lucca- (n=lucca@kuu.accela.net) joined #forth 15:27:02 Our private version does, but we've hacked on it significantly. 15:29:15 We've also tweaked it so that we forbid writing to the dictionary if we don't have a compiler attached (a read-only run-only mode). 15:31:01 I've got some work planned to split the dictionary into read-only and read-write sections so that we can run the core out of ROM and still allow compilation to extend the dictionary. 15:46:32 --- join: foxchip (n=fox@166.129.78.203) joined #forth 15:51:34 --- join: nighty^ (n=nighty@210.188.173.246) joined #forth 16:09:12 --- quit: forther ("Leaving") 16:36:58 --- join: Al2O3 (n=Al2O3@c-76-120-54-133.hsd1.co.comcast.net) joined #forth 16:51:02 --- quit: proteusguy (Connection timed out) 16:52:11 --- join: proteusguy (n=proteusg@ppp-124-120-216-236.revip2.asianet.co.th) joined #forth 17:25:38 --- quit: foxchip (Read error: 110 (Connection timed out)) 17:33:13 --- quit: tathi ("leaving") 17:50:41 --- quit: JasonWoof ("Leaving.") 18:15:22 --- join: JasonWoof (n=JasonWoo@unaffiliated/herkamire) joined #forth 18:15:22 --- mode: ChanServ set +o JasonWoof 18:45:06 sweeet I figured out how to move windows aronud with the keyboard properly when I've got wmii split into columns 18:45:39 now I can rule the world! muahahaha! 18:46:00 dunno if I can resize them with the keyboard, but that's ok 20:16:58 "I'm all alone. There's nobody here beside meeeeee" 20:18:49 * gnomon is here too 20:20:43 awww 20:21:46 * slava can't remember he last saw some forth discussion in here 20:21:52 the thought had accured to me that if I said something interesting I might get response 20:22:40 yesterday viric came in and was asking about making binaries 20:23:14 Well, on that topic, could anyone here suggest a native-code-compiling Forth for an ARMv5 chip, hopefully with a built-in assembler (and, better yet, a dissassembler)? 20:23:24 I told him that you can make shell script type executables with gforth (what he was using) but that Ididn't think you could make sand-alone executables 20:24:14 If you didn't mind using gforth, you could save out a heap image and, I think, build a binary version of gforth which loads that heap upon invocation. 20:24:26 yeah? 20:24:28 that's nifty 20:25:00 I'm not sure if that's in the documentation, but I think it is. It may have been a lengthy post on the mailing list. 20:25:07 heh 20:25:22 I might like gforth if it was well documented 20:27:27 there's been a fair bit of arm discussion in here, but I'm afraid none of it stuck in my little brain 20:28:10 somebody was working on a forth for the game boy advanced 20:28:13 iirc that'ts arm 20:48:14 --- quit: nighty^ ("Disappears in a puff of smoke") 20:48:22 --- join: nighty^ (n=nighty@210.188.173.246) joined #forth 20:49:02 'Tis; that was probably PandaForth, though I wasn't involved in the discussion. 20:52:53 --- join: skas (n=skas@c-24-61-243-42.hsd1.ma.comcast.net) joined #forth 20:52:56 --- quit: skas (Read error: 104 (Connection reset by peer)) 22:00:58 man, working makes me grumpy sometimes 22:01:56 I allotted 10 minutes to update a page, but it turned out to be made from a massive derranged table filled mostly with solid purple images of various shapes. 22:02:07 you'd think the solid background color would work... but no! 22:02:27 I ended up deleting most of it and arranging the 5 things myself 22:04:15 between trying to edit, recoding, and actually making the change it took me almost an hour 22:29:15 --- quit: arke (Read error: 104 (Connection reset by peer)) 22:36:45 --- join: sauvin (i=sauvin@c-98-213-79-115.hsd1.il.comcast.net) joined #forth 23:36:38 what is the name of the TIL book? The classic? 23:37:55 http://www.amazon.com/Threaded-Interpretive-Languages-Design-Implementation/dp/007038360X 23:38:03 tx 23:38:26 np 23:38:44 --- quit: Al2O3 () 23:59:59 --- log: ended forth/08.02.21