00:00:00 --- log: started forth/14.12.17 00:36:31 --- quit: mnemnion (Remote host closed the connection) 01:20:08 --- join: impomatic (~chatzilla@140.62.115.87.dyn.plus.net) joined #forth 01:50:31 --- quit: fantazo (Quit: Verlassend) 02:40:15 --- quit: tangentstorm (Quit: WeeChat 0.3.2) 03:04:08 --- quit: true-grue (Read error: Connection reset by peer) 03:09:38 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 03:14:39 --- quit: nighty^ (Remote host closed the connection) 03:18:03 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 03:21:14 --- quit: Bahman (Ping timeout: 250 seconds) 03:28:11 --- quit: samrat (Quit: Computer has gone to sleep.) 03:31:16 --- join: samrat (~samrat@61.12.96.226) joined #forth 03:31:49 --- quit: samrat (Client Quit) 03:37:36 --- join: Bahman (~Bahman@84.241.8.144) joined #forth 03:49:14 --- quit: protist (Ping timeout: 256 seconds) 03:56:26 --- join: samrat (~samrat@61.12.96.226) joined #forth 04:05:45 --- quit: samrat (Quit: Computer has gone to sleep.) 04:09:37 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 04:10:21 --- quit: Zarutian (Read error: Connection reset by peer) 04:10:25 --- join: kumul (~mool@adsl-64-237-239-22.prtc.net) joined #forth 04:10:37 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 04:23:06 --- quit: Bahman (Ping timeout: 264 seconds) 04:30:41 --- join: impomatic_ (~digital_w@140.62.115.87.dyn.plus.net) joined #forth 04:59:25 --- join: saml_ (~saml@pool-71-190-5-214.nycmny.east.verizon.net) joined #forth 05:57:27 --- quit: kumul (Ping timeout: 265 seconds) 05:59:27 --- quit: saml_ (Quit: Leaving) 06:01:44 --- join: Azel (~Thunderbi@ANice-653-1-421-91.w83-201.abo.wanadoo.fr) joined #forth 06:10:28 --- join: mayuresh (~mayuresh@triband-mum-120.60.170.16.mtnl.net.in) joined #forth 06:11:13 hello :) 06:11:29 would michael richter be around by any chance? 06:13:38 i guess not! 06:13:45 bye ... :) 06:13:46 --- quit: mayuresh (Client Quit) 06:21:01 --- join: mayuresh (~mayuresh@triband-mum-120.60.170.16.mtnl.net.in) joined #forth 06:21:07 --- quit: mayuresh (Client Quit) 06:56:37 --- join: samrat (~samrat@123.236.183.195) joined #forth 07:03:23 --- join: kumul (~mool@adsl-64-237-238-22.prtc.net) joined #forth 07:11:32 --- quit: darkf (Quit: Leaving) 07:14:16 --- quit: samrat (Quit: Computer has gone to sleep.) 07:19:45 --- join: samrat (~samrat@123.236.183.195) joined #forth 07:29:36 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 08:13:01 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 08:53:19 --- join: true-grue (~grue@95-27-145-177.broadband.corbina.ru) joined #forth 10:24:44 --- quit: irsol (Ping timeout: 264 seconds) 10:31:55 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 10:51:46 --- quit: kumul (Ping timeout: 256 seconds) 11:16:50 --- join: mark4_ (~mark4@cpe-68-203-183-77.tx.res.rr.com) joined #forth 11:17:15 does anyone here have any experience working with the IAR deveopment tools? 11:23:58 --- quit: ASau (Remote host closed the connection) 11:24:06 --- quit: samrat (Ping timeout: 264 seconds) 11:25:44 --- join: ASau (~user@46.114.142.176) joined #forth 11:26:34 --- join: samrat (~samrat@123.236.183.195) joined #forth 11:30:36 --- join: sivteck (~sivteck@unaffiliated/sivteck) joined #forth 11:30:54 --- quit: samrat (Ping timeout: 258 seconds) 11:32:08 --- join: samrat (~samrat@123.236.183.195) joined #forth 11:38:23 --- quit: samrat (Ping timeout: 245 seconds) 11:41:15 --- join: samrat (~samrat@123.236.183.195) joined #forth 11:47:56 --- quit: Zarutian (Quit: Leaving.) 11:57:32 --- part: sivteck left #forth 12:01:57 --- quit: samrat (Ping timeout: 244 seconds) 12:08:00 --- join: samrat (~samrat@123.236.183.195) joined #forth 12:17:02 --- join: malyn_ (~malyn@unaffiliated/malyn) joined #forth 12:18:36 --- quit: malyn (Ping timeout: 240 seconds) 12:18:36 --- nick: malyn_ -> malyn 12:23:48 --- quit: mark4 (Remote host closed the connection) 12:35:25 --- quit: samrat (Ping timeout: 256 seconds) 12:36:27 --- quit: mark4_ (Quit: Leaving) 12:39:38 --- join: samrat (~samrat@123.236.183.195) joined #forth 12:42:15 --- quit: samrat (Client Quit) 12:54:32 --- join: Mat4 (~claude@ip5b406773.dynamic.kabel-deutschland.de) joined #forth 12:54:36 hello 12:57:43 --- part: Mat4 left #forth 13:04:58 --- join: Mat4 (~claude@ip5b406773.dynamic.kabel-deutschland.de) joined #forth 13:40:55 --- quit: true-grue (Read error: Connection reset by peer) 14:14:33 --- join: kumul (~mool@adsl-64-237-238-214.prtc.net) joined #forth 14:31:21 --- quit: proteusguy (Ping timeout: 255 seconds) 14:33:13 --- quit: joneshf-laptop (Remote host closed the connection) 14:37:07 --- quit: gabriel_laddel (Ping timeout: 258 seconds) 14:37:20 howdy 14:37:27 i'm thinking we should all write bots to say hi back to you. so you don't get lonely and leave ;) 14:44:40 --- join: proteusguy (~proteusgu@ppp-110-168-229-74.revip5.asianet.co.th) joined #forth 14:44:40 --- mode: ChanServ set +v proteusguy 15:00:22 we should have a forth bot. (that says hello) 15:11:50 Bots saying hello is a bit of a pain. 15:12:23 But if I could post a code example here and the bot would run it and show the results, that might be handy 15:36:04 yeah... I was thinking of the second idea 15:38:12 --- quit: TodPunk (Ping timeout: 245 seconds) 15:38:20 "begin s" Hello Everybody!" type again"... a PITA bot 15:38:33 and would get kicked pretty fast. 15:38:50 --- quit: Azel (Ping timeout: 240 seconds) 15:39:22 --- join: Azel (~Thunderbi@ANice-653-1-421-91.w83-201.abo.wanadoo.fr) joined #forth 15:47:59 forth bot is a good concept... but *which* forth could be the ultimate flame fest! ;-) 15:49:37 And wouldn't we need an instance per irc handle so the stacks/dictionaries don't collide? Would be like a multi-user forth. 15:50:03 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 15:50:38 ...and a forth bot should say "ok" not "hello" ;) 15:51:26 lol... yes. 15:53:51 maybe it could just listen in the room and accept source from specially formatted messages 15:54:22 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 15:54:32 bot: .( hello world) 15:54:42 something like that. 15:55:17 Or it could just attempt to interpret every line that comes in and execute only the valid ones. Consider everything else a comment. 15:56:08 yeah.. 15:57:06 maybe we could just replace ACCEPT with IRC w/ filter 16:03:29 --- quit: impomatic (Ping timeout: 240 seconds) 16:03:49 --- quit: impomatic_ (Ping timeout: 240 seconds) 16:06:44 I think someone mentioned a sandbox machine too. 16:06:54 something like that might work but it needs to route to the correct user based on the source irc handle. 16:07:27 maybe a stripped down virtual machine might do. 16:08:04 we might want to start off with a machine that isn't multi-user. 16:09:04 err... lemme rephrase: a *forth* that's not multi-user. 16:09:39 so you mean a unique forth machine per requesting irc handle? 16:15:25 maybe. or, at first, just a regular single user forth hooked up to the channel. 16:16:00 everybody can just blam source input into the machine. 16:16:17 *We* would have to cooperatively use it. 16:17:11 if that works, then maybe do multi-user based on msg sender's nicks 16:17:37 --- quit: nighty^ (Read error: Connection reset by peer) 16:17:44 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 16:19:29 IIRC, IRC is really easy to talk. 16:21:46 beretta, the other option is simply that every forth input has to be the complete expression and the context/stack gets reset each time. maybe newly defined words can be remembered. 16:23:14 haha - i love where my 0.01-baked idea has gone. really i just thought of bots to say 'hi' back to mat3/4 since he comes in every day and says hi to the room 16:23:27 and i feel bad when nobody gets to him before he's gone 16:24:21 well you know programmers - we gotta over-engineer everything. :) 16:24:40 1- irc is a pretty simple protocol, yes. 2- many other bots respond to 'dot-commands' - any msg prefixed with something like .do would cause it to attempt to run the rest of the msg as forth, e.g. 16:25:13 so it only does stuff when you want it to - less annoying than having it try to be "smart" 16:26:35 if you're on a linux, the program 'sic' is a "simple irc client" and acts basically like netcat and allows nearly raw access to the protocol via stdin/out - so wouldn't be too hard to tie it into a forth running on someone's system 16:27:11 the rest is left as an exercise to the reader ;) 16:31:32 --- join: bk-bot (~bk-bot@2001:470:1:41:8cd5:ab1a:314e:6b2f) joined #forth 16:31:42 --- quit: bk-bot (Client Quit) 16:32:52 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 16:33:15 maybe some fail-safe can be built in so it won't blam the channel. 16:35:02 ' : himat3 s" mat4" onjoin .( Hi Mat4!) cr ' 16:35:11 :) 16:40:20 I'm a bit more concerned about the bot host machine getting whacked. People would have to be 'polite'. 16:42:07 nice the proc and don't give it file system access? or only have it accept commands from its owner/trusted people/etc. 16:43:01 yeah, no filesystem access. maybe just some old-school blocks (virtualized of course) 16:43:05 whomever runs it can do whatever they want to self-protect. including nothing. as long as it doesn't spam the channel i'd welcome any/all comers 16:44:01 I'll see if I can get my virtual linux server working. 16:47:25 --- part: Mat4 left #forth 16:48:58 bye Mat4 ! :) 16:49:39 I don't know what the IRC rules are for bots. 16:50:22 I believe I still have a physical experimental ARM box hosted in france. Happy to give someone access to setup the bot there if they wanna try it out. 16:51:49 I have a ngaro-style VM forth that does indeed compile and a raspi. 16:54:21 beretta: ngaro-style? So an VM that is similiar to the ngaro vm but not quite same? 16:56:03 yeah... the one RetroForth uses. Mines a bit more 16 bit friendly, as I was intending on using it on a 64k 6809 based Color Computer 16:56:14 I see 16:56:19 --- join: protist (~javery@60.253.69.111.dynamic.snap.net.nz) joined #forth 16:57:46 but I did create a C engine for it. Maybe I can shoe-horn in a IRC backend to "KEY" 17:01:19 I got a bit crazy three months back and made an FCPU spec mainly because I wanted to use something like the DCPU-16 used for interfacing with 'hardware' devices. 17:03:13 --- quit: ASau (Remote host closed the connection) 17:04:54 I must admit I need to google DCPU-16. 17:05:08 --- join: ASau (~user@46.114.142.176) joined #forth 17:19:19 looks like an interesting game. 17:21:42 I just liked that the HW interface isnt in the same address space as main memory 17:22:10 ah 17:24:17 and I decided to make the CPU itself fully re-virtualizable (a property named after two guys whose names I dont recall at the moment) 17:29:44 lol... right 17:30:01 *those* guys! :) 17:30:57 Zarutian, are you saying you designed your own stack machine processor? This is actually something I'm very interested in. 17:31:11 I do not remember the names but I remember the property. 17:31:21 proteusguy: more like a VM spec 17:33:01 it is barely more than 32 or so 'primitives' that go from $00-$1f. Anything about $1f is treated as a call to that address. 17:33:11 Ah - it's a virtual cpu inside a game right? 17:33:33 can be 17:34:18 didnt want to muck about with bit fields like done with Novix 4016 and such that are described in "Stack Machines: The New Wave" 17:34:45 haha well that's more along my direction actually. 17:35:18 I have looked at all those described in that book and J1 from excamera also 17:36:21 unencoded instructions are neat 17:38:42 having the cell size equiv to memory address size is also neat 17:41:00 yep 17:41:54 toyed a bit with a preliminary draft to a spec of a version of J1 that used 24 bit addresses and cells. 17:48:19 --- join: ASau` (~user@46.114.178.25) joined #forth 17:51:06 --- quit: ASau (Ping timeout: 245 seconds) 17:52:38 well, I am off to bed 17:53:03 --- quit: Zarutian (Quit: Leaving.) 17:53:33 --- nick: ASau` -> ASau 18:08:47 How does one get a copy of isforth now? The website is down for the moment. 18:09:17 internet archives? way back machine? though they may not cache non-html files 18:09:35 or hang out and ask the author then he pops back in 18:10:12 i have 1.24b (source) i can put online if you want 18:11:02 waybackmachine did indeed cache it. thanx. 18:11:37 i also just put a copy at http://bluekelp.com/isforth-1.24b.tar.bz2 18:31:43 --- quit: ASau (Remote host closed the connection) 18:34:55 --- join: ASau (~user@46.114.178.25) joined #forth 18:35:42 Hmm... compiled and extended it but it doesn't like my terminal. 18:35:45 scherrey@redsky:~/develop/forth/isforth-1.24b$ ./isforth 18:35:45 Unknown TERM: /usr/share/terminfo/x/xterm 18:35:46 Au Revoir! 18:39:05 bluekelp, you ever run into this? 18:46:10 i have not. not even sure i've compiled and run it yet :) 18:46:26 try: 18:46:36 TERM=vt100 ./isforth 18:48:06 --- quit: ASau (Ping timeout: 250 seconds) 18:48:12 did that work for you? I got a funny looking screen (looks like curses gunk) then a floating point exception core dump. 18:51:04 TERM=xterm-utf8 ./isforth worked! 18:51:25 Strange that an odd term setting would result in a floating point crash. 18:52:08 nice. i actually don't think i've compiled and run it yet :) 18:52:35 --- join: ASau (~user@46.114.178.25) joined #forth 19:00:06 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 19:13:54 --- quit: kumul (Quit: Leaving) 19:49:23 --- quit: ASau (Read error: Connection reset by peer) 19:49:23 --- join: ASau` (~user@46.114.178.25) joined #forth 19:53:34 --- nick: ASau` -> ASau 20:45:20 --- join: samrat (~samrat@123.236.183.195) joined #forth 21:05:55 --- quit: samrat (Quit: Computer has gone to sleep.) 21:18:35 --- quit: nisstyre (Changing host) 21:18:35 --- join: nisstyre (~yourstrul@oftn/member/Nisstyre) joined #forth 21:47:46 --- join: samrat (~samrat@61.12.96.226) joined #forth 22:09:54 --- quit: samrat (Quit: Computer has gone to sleep.) 22:21:55 --- join: samrat (~samrat@61.12.96.226) joined #forth 22:37:53 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 23:32:48 --- join: true-grue (~grue@95-27-185-33.broadband.corbina.ru) joined #forth 23:39:26 --- quit: mnemnion (Remote host closed the connection) 23:42:50 --- join: sivteck (~sivteck@unaffiliated/sivteck) joined #forth 23:43:28 --- part: sivteck left #forth 23:50:39 --- quit: samrat (Quit: Computer has gone to sleep.) 23:59:59 --- log: ended forth/14.12.17