00:00:00 --- log: started forth/11.11.20 00:04:55 --- join: ygrek (~user@gateway/tor-sasl/ygrek) joined #forth 00:05:52 --- quit: Gmind (Ping timeout: 240 seconds) 00:12:26 --- quit: ygrek (Ping timeout: 248 seconds) 00:21:06 --- quit: schme (Read error: Operation timed out) 00:24:58 --- join: schme (~marcus@c83-254-190-169.bredband.comhem.se) joined #forth 00:25:00 --- quit: schme (Changing host) 00:25:00 --- join: schme (~marcus@sxemacs/devel/schme) joined #forth 00:35:44 --- join: ygrek (~user@gateway/tor-sasl/ygrek) joined #forth 01:09:17 --- join: Gmind (~nevermind@113.190.187.231) joined #forth 01:17:02 --- quit: Gmind (Ping timeout: 240 seconds) 03:15:11 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 03:58:35 --- join: _spt_ (~postmaste@host-92-4-99-123.as43234.net) joined #forth 03:58:35 --- quit: _spt_ (Changing host) 03:58:35 --- join: _spt_ (~postmaste@unaffiliated/-spt-/x-5624824) joined #forth 04:16:54 The project at http://forthos.org/ – is it dead? 04:17:03 Or has it moved somewhere else? 04:22:32 <_spt_> have you seen this Linux/Forth ISO http://home.hccnet.nl/a.w.m.van.der.horst/lina.html 04:28:20 --- quit: MayDaniel (Read error: Connection reset by peer) 04:32:10 _spt_: Thanks for the pointer. I'm mostly interested, however, in using a Forth basis for experimenting with kernel architectures dynamically. 04:32:43 I'll be downloading that (because I can always use another bizarre Forth!:D) but I'm curious still at what happened to the pure-Forth version. 04:33:36 <_spt_> ttmrichter : looks like ForthOS last post was sept 2005, so the project could be dead 04:34:07 <_spt_> which is a shame, I only wish there was a more active Forth groups in the UK 04:37:51 <_spt_> As foar as I can work out the only active hobby Forth groups are the Figition project and the Jupiter Ace Archive 04:37:58 <_spt_> http://sites.google.com/site/libby8dev/fignition 04:38:14 <_spt_> http://www.jupiter-ace.co.uk/ 04:39:55 <_spt_> I'm waiting for the Raspbarry Pi computer , in the nest twe weeks to come out to use it as a linux/gforth to teach some programming to some kids 04:40:12 It looks like ForthOS is dead, yes, but it looks like enough is there to use as a foundation for my project. 04:40:25 And what's Raspberry Pi? 04:40:28 <_spt_> at only $25 cheap 04:40:40 <_spt_> http://www.raspberrypi.org/ 04:41:55 <_spt_> see http://www.youtube.com/watch?gl=GB&v=q19aEikc3JI 05:20:40 --- quit: nottwo (*.net *.split) 05:20:43 --- quit: koisoke (*.net *.split) 05:20:43 --- quit: saper (*.net *.split) 05:20:46 --- join: nottwo (~trannie@nottwo.org) joined #forth 05:20:51 --- join: koisoke (xef4@epilogue.org) joined #forth 05:20:53 --- join: saper (saper@wikipedia/saper) joined #forth 05:46:42 _spt_:Ooh! That looks like a nice toy! 05:46:53 I'll definitely consider doing a bare-metal Forth on that box! 05:47:26 <_spt_> yes look fun, I plan to get two one for my sons to play with 05:53:06 And in other news of awesomeness, I got ForthOS to boot under VirtualBox. 05:53:11 The project may be dead, but it's functional. 05:53:34 And now my dream of experimenting with exokernels can come true. 05:53:35 <_spt_> oh great I might have a play with that laster 05:54:01 You'll want a copy of Damn Small Linux or the like to prep the file system. 05:54:08 <_spt_> what are you hoping to do? 05:54:16 (And to fix things up for when you've blown away your ForthOS partition by accident.) 05:54:40 I like Forth for the ability to work hard down at the bare metal while still being able to quickly and easily build abstractions. 05:55:01 I figure for OS designs Forth would be a brilliant exploratory tool. 05:55:45 For the '386+ line, for example, I could use the built-in assembler (I'm hoping ForthOS has one, if not I'll have to write it) to screw around with all those stupid tables that Intel insisted on inflicting upon the world. 05:55:59 The GDT, LDT, ThisDT, ThatDT, etc. 05:56:26 Wrap up the creation of those in low-level words and then never worry about them again as I toy around with high-level abstraction chains. 05:56:33 <_spt_> If ForthOS works fine in VM , then is should work on the R Pi machine 05:56:45 Well, the R Pi machine is an ARM. 05:56:55 The assembler core will have to get modified, of course. 05:57:01 But it's looking like a good start. 05:58:48 It boots in about half a second flat too. :) 05:59:03 It takes longer for GRUB to load than it does for ForthOS itself. :) 06:00:33 <_spt_> did you burn the ForthOS to CD first? 06:32:10 _spt_: I used the ISO file directly in VirtualBox. 06:32:22 First I booted DSL and installed it to the second partition on a virtual disk. 06:32:43 Then I booted it again from the virtual hard drive and set up ForthOS (and the GRUB menu). 06:32:47 Then I booted ForthOS. 06:39:55 <_spt_> thanks, I have to pop out now, brb later. ( off the get my dinner from the allotmet!) 06:41:43 --- quit: ttmrichter (Read error: Connection reset by peer) 07:13:31 --- join: Gmind (~nevermind@113.190.166.115) joined #forth 07:31:00 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 07:57:42 --- quit: _spt_ (Quit: Leaving) 07:59:42 --- quit: Gmind (Quit: Leaving.) 08:05:44 --- quit: MayDaniel (Read error: Connection reset by peer) 08:08:18 --- join: _spt_ (~postmaste@host-92-4-99-123.as43234.net) joined #forth 08:08:18 --- quit: _spt_ (Changing host) 08:08:18 --- join: _spt_ (~postmaste@unaffiliated/-spt-/x-5624824) joined #forth 11:03:36 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 11:12:57 --- quit: MayDaniel (Read error: Connection reset by peer) 11:47:02 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 11:47:11 --- quit: MayDaniel (Read error: Connection reset by peer) 12:19:55 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 12:22:55 --- quit: MayDaniel (Read error: Connection reset by peer) 12:40:11 --- join: erider (~chatzilla@unaffiliated/erider) joined #forth 12:58:37 --- part: erider left #forth 13:02:25 --- join: Bahman (~user@2.146.44.190) joined #forth 13:02:30 Hi all! 13:06:31 Hi! 13:07:15 <_spt_> evening 13:11:41 --- quit: Snoopy_1711 () 13:31:13 --- quit: neena (Ping timeout: 240 seconds) 13:32:48 --- join: neena (~neena@76.73.121.203) joined #forth 13:38:00 --- join: tathi (~josh@dsl-216-227-95-32.fairpoint.net) joined #forth 13:44:45 --- quit: Bahman (Remote host closed the connection) 13:48:08 --- part: _spt_ left #forth 13:55:04 --- quit: ygrek (Ping timeout: 248 seconds) 14:01:01 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 14:08:51 --- join: _spt_ (~postmaste@host-92-4-99-123.as43234.net) joined #forth 14:08:51 --- quit: _spt_ (Changing host) 14:08:51 --- join: _spt_ (~postmaste@unaffiliated/-spt-/x-5624824) joined #forth 14:24:14 <_spt_> In gforth is there a word to stop the 'pk' prmpt being prints to the screen, in jupiter ace forth its INVIS, I can not find it in gForth 14:25:40 --- quit: MayDaniel (Read error: Connection reset by peer) 14:46:20 --- join: ttmrichter (~ttmrichte@113.106.101.45) joined #forth 15:14:53 _spt_: looks like it's hard-coded 15:15:09 <_spt_> thanks, 15:15:19 <_spt_> got another question .. 15:16:04 ttmrichter: you could probably use the x86 assembler from Win32Forth if ForthOS doesn't have one. 15:16:20 <_spt_> why when you use see that has a ." text " in it I see .\" test " where does the extra \ come from? 15:16:28 Or Albert van der Horst's ciasdis ... or something. You probably shouldn't have to write your own... 15:16:49 tathi: ForthOS has an assembler. :) 15:16:57 Gforth has s\" and other similar words which accept \escapes. 15:17:28 ." and friends compile the same runtime code, so that's how SEE disassembles it. 15:17:31 ttmrichter: oh, good. :) 15:18:50 _spt_: make sense? 15:18:59 <_spt_> no! 15:19:08 There's a word .\" 15:19:21 So you could write .\" Foo:\n\tbar" 15:19:28 and you would get a return and a tab. 15:20:20 ." doesn't accept the backslash codes, but when it compiles a string, you can't tell whether it was compiled by ." or .\" 15:20:40 So whoever wrote SEE decided to make the disassembly show .\" 15:21:38 Better? Or should I try again? :) 15:21:41 <_spt_> I see like in C, so ." and .\" are the same, but in gforth it looking for escape code so whe I list - SEE the word I should see .\" 15:21:54 Yup. 15:21:57 <_spt_> thanks 15:22:21 Well, they're not exactly the same; if you write ." \n" you will get a backslash and an 'n'. 15:22:42 <_spt_> I understand now :-) 15:23:11 <_spt_> I wish there was an active Forth group in the uk! 15:28:58 AFAICT there isn't an active Forth group anywhere, except the silicon valley 15:29:54 <_spt_> there are two gruops active in the UK, the Fignation forth computer and the Jupiter Ace achive project 15:30:18 --- quit: ttmrichter (Quit: Leaving) 15:30:19 Oh, there's a Dutch forth group as well. 15:30:51 <_spt_> http://sites.google.com/site/libby8dev/fignition 15:31:16 Yeah, FIGnition is just in the last 8 months or so, isn't it? 15:31:41 <_spt_> yes, I have one sitting here on my desk 15:32:20 <_spt_> Maybe I should start a forth group 15:34:50 You could contact MPE and ask them if they know of other Forth hobbyists in your area. 15:36:40 <_spt_> I just might do that, 30 years ago there was a guy a Keele Uni I did a few weeks with him 15:37:51 Also, it looks like the Euroforth conference is probably due to be in England again next year, so if you think of it next September... 15:39:26 <_spt_> I guess that will be over my head, 15:39:58 Maybe not by then... :) 15:40:10 <_spt_> I'm thinking of taking half a dozen Jupiter Aces next sunduy to a reto show 15:40:19 <_spt_> http://www.retrocomputermuseum.co.uk/ 15:41:11 Interesting. Not really my thing, but interesting. :) 15:42:04 <_spt_> its not my thing really, they just want to see some Jupiter Aces! 15:49:42 --- join: Snoopy_1611 (Snoopy_161@dslb-088-069-141-167.pools.arcor-ip.net) joined #forth 15:58:15 <_spt_> night all. 15:58:19 --- part: _spt_ left #forth 16:00:10 --- quit: Snoopy_1611 () 17:02:11 --- join: dzho (~deejoe@poppy.etrumeus.com) joined #forth 17:07:26 --- quit: Fox78 (Ping timeout: 245 seconds) 17:50:04 --- join: ttmrichter (~ttmrichte@58.56.112.93) joined #forth 18:01:38 --- join: Fox78 (~fox@123.121.64.18) joined #forth 18:12:21 --- quit: tathi (Quit: leaving) 18:12:34 --- quit: Fox78 (Ping timeout: 248 seconds) 18:17:12 --- join: Fox78 (~fox@123.121.64.18) joined #forth 19:21:37 --- join: redworlf (~yangyitao@118.242.1.66) joined #forth 19:23:10 --- quit: redworlf (Client Quit) 19:41:18 --- quit: neena (Changing host) 19:41:19 --- join: neena (~neena@unaffiliated/neenaoffline) joined #forth 19:55:59 --- join: Snoopy_1611 (Snoopy_161@dslb-188-107-193-048.pools.arcor-ip.net) joined #forth 21:24:58 --- quit: ttmrichter (Quit: Leaving) 22:17:48 --- join: Gmind (~nevermind@123.16.231.75) joined #forth 22:18:14 --- quit: Gmind (Client Quit) 23:32:06 --- quit: neena (Ping timeout: 258 seconds) 23:38:42 --- join: neena (~neena@76.73.121.203) joined #forth 23:46:36 --- quit: neena (Ping timeout: 252 seconds) 23:48:15 --- join: neena (~neena@76.73.121.203) joined #forth 23:54:09 --- quit: neena (Ping timeout: 260 seconds) 23:54:14 --- join: neena (~neena@76.73.121.203) joined #forth 23:59:59 --- log: ended forth/11.11.20