00:00:00 --- log: started forth/16.10.30 00:08:20 --- quit: nal (Quit: WeeChat 1.4) 01:23:43 --- join: neceve (~ncv@86.125.241.206) joined #forth 01:23:43 --- quit: neceve (Changing host) 01:23:43 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 02:06:11 --- quit: nighty-_ (Ping timeout: 260 seconds) 02:10:26 --- join: nighty- (~cp@www.taiyolabs.com) joined #forth 02:49:14 --- join: true-grue (~true-grue@176.14.222.10) joined #forth 04:10:20 proteusguy: that was either a crazy long reboot or a short nap 04:12:51 --- quit: mnemnion (Remote host closed the connection) 05:37:45 I'm trying to install a new OS on my desktop and had to try the boot media on my laptop (this machine) first. Having issues... 06:24:28 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:e1cc:2cab:8e3a:2f10) joined #forth 06:29:06 --- quit: mnemnion (Ping timeout: 260 seconds) 06:35:32 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 07:03:10 --- quit: ricky_ricardo (Ping timeout: 260 seconds) 07:13:09 --- join: rgrinberg (~rgrinberg@blk-212-79-74.eastlink.ca) joined #forth 07:50:34 I propose the Forth SMS challange. Fit a usefull word definition or program in 140 characters or less (unicode allowed). Multiple SMSes allowed though but something like --> is then needed. ( perahaps sms--> has the stack effect of ( currSMSnr nextSMSnr -- ) 07:55:34 Classical challenges for Forth were 1 BLOCK related. 07:55:45 You may also use CF BLOCK :) 08:19:02 --- join: joneshf-laptop (~joneshf@c-73-220-86-28.hsd1.ca.comcast.net) joined #forth 08:24:40 --- nick: eldre -> eldre__ 08:31:06 --- quit: eldre__ (Read error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number) 08:34:08 --- join: eldre (~eldre@blip.afturgurluk.net) joined #forth 08:44:24 --- quit: joneshf-laptop (Quit: Leaving) 08:44:38 --- join: joneshf-laptop (~joneshf@c-73-220-86-28.hsd1.ca.comcast.net) joined #forth 08:45:31 --- quit: joneshf-laptop (Remote host closed the connection) 08:45:43 --- join: joneshf-laptop (~joneshf@c-73-220-86-28.hsd1.ca.comcast.net) joined #forth 08:47:11 --- quit: joneshf-laptop (Read error: Connection reset by peer) 08:47:23 --- join: joneshf-laptop (~joneshf@c-73-220-86-28.hsd1.ca.comcast.net) joined #forth 08:50:34 --- quit: rgrinberg (Ping timeout: 244 seconds) 08:53:33 --- join: desolator (~quassel@broadband-188-255-97-129.nationalcablenetworks.ru) joined #forth 09:31:40 --- quit: dys (Ping timeout: 245 seconds) 09:32:59 --- join: dys (~dys@ip-109-44-2-62.web.vodafone.de) joined #forth 10:01:45 --- nick: karswell` -> karswell 11:15:10 --- join: ids1024 (~ids1024@unaffiliated/ids1024) joined #forth 11:17:07 --- quit: karswell (Read error: Connection reset by peer) 12:04:18 --- quit: dys (Ping timeout: 250 seconds) 12:11:21 --- join: dys (~dys@ip-109-44-2-75.web.vodafone.de) joined #forth 12:24:45 --- join: nal (~nal@adsl-64-237-237-31.prtc.net) joined #forth 12:31:32 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:d995:33d8:5b97:580a) joined #forth 12:32:02 --- quit: neceve (Quit: Konversation terminated!) 12:35:50 --- quit: mnemnion (Ping timeout: 245 seconds) 12:54:56 --- quit: nal (Quit: WeeChat 1.4) 12:59:45 --- join: ASau` (~user@89.15.237.203) joined #forth 13:01:27 --- quit: ASau (Read error: Connection reset by peer) 13:02:50 --- nick: ASau` -> ASau 13:35:11 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:6051:50fe:b6bc:162f) joined #forth 13:39:50 --- quit: mnemnion (Ping timeout: 260 seconds) 13:43:56 --- join: nal (~nal@adsl-64-237-237-31.prtc.net) joined #forth 13:48:16 --- join: rgrinberg (~rgrinberg@blk-222-202-216.eastlink.ca) joined #forth 13:54:16 --- quit: desolator (Remote host closed the connection) 14:03:02 --- quit: nal (Quit: WeeChat 1.4) 14:15:48 --- quit: rgrinberg (Remote host closed the connection) 14:16:25 --- join: nal (~nal@adsl-64-237-237-31.prtc.net) joined #forth 14:45:04 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 15:44:19 --- quit: true-grue (Read error: Connection reset by peer) 16:33:17 It truely amazing what can be achieved with only 512Bytes of return stack 16:44:31 OriansJ: what sized cells? 512 Bytes seems huge. 16:45:58 4bytes 16:49:01 128 cells deeps is still huge :) 16:50:59 beretta: True, originally I allocated 1MB for the return stack but oh the lessons one learns while writting a forth. 16:52:01 My particular favorite is executing the stack :) 16:52:39 it worked in the old days, at least :) 16:52:54 beretta: Ever push your name onto the return stack and checked to see what happened? 16:53:28 oh cool... I gotta try that. 17:04:44 --- quit: nighty (Quit: Disappears in a puff of smoke) 17:15:20 --- join: ricky_ricardo (~rickyrica@2601:240:4203:ecb0:5d05:c822:c39e:8ec1) joined #forth 17:30:12 --- join: karswell (~user@124.209.208.46.dyn.plus.net) joined #forth 17:51:12 --- join: nighty (~nighty@d246113.ppp.asahi-net.or.jp) joined #forth 18:03:16 --- join: djose (c8d80621@gateway/web/freenode/ip.200.216.6.33) joined #forth 18:31:40 --- quit: Zarutian (Quit: Zarutian) 18:56:53 --- quit: djose (Ping timeout: 260 seconds) 19:02:11 Well using Jones Forth as a template allowed me to write a Forth in a day, but thus far debugging the translation errors has massively exceeded the original development time. 19:04:25 https://github.com/oriansj/stage0/blob/master/stage2/forth.s 19:05:06 Still has bug fixing left to do to make it actually useful [Its really buggy] 19:22:07 --- join: djose (c8d80621@gateway/web/freenode/ip.200.216.6.33) joined #forth 19:43:19 OriansJ: can you return stack be inscreased dynamiclly 19:46:10 --- quit: ricky_ricardo (Ping timeout: 260 seconds) 19:59:10 --- join: ricky_ricardo (~rickyrica@2601:240:4203:ecb0:87c:e319:2ff4:eead) joined #forth 20:06:15 --- join: neceve (~ncv@86.125.241.206) joined #forth 20:06:15 --- quit: neceve (Changing host) 20:06:15 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 20:13:47 --- nick: djose -> dcs 20:40:44 --- quit: dcs () 20:40:51 --- join: rgrinberg (~rgrinberg@24-246-56-85.cable.teksavvy.com) joined #forth 21:52:35 BIND implementations in various forths: http://hub.darcs.net/pointfree/forth-bind 21:53:06 BIND is great for CMForth style cross compilation 21:54:26 --- quit: neceve (Quit: Konversation terminated!) 22:00:11 In fact, I'm using it in the { and } words to bind C! C@ to openocd SWD versions and DP to a target or subspace and I can continue using already defined words such as ALLOT and HERE without redefining them for the alternate dictionary pointer. 22:04:34 --- quit: nal (Quit: WeeChat 1.4) 22:05:55 I'm thinking nested subspaces with { and } would be a good idea. 22:07:48 I would use a space for the host, a space for the target, a subspace for the target interrupt vector table, a subspace for the dictionary and so on. 22:09:49 --- quit: pointfree (Remote host closed the connection) 22:10:01 --- join: pointfree (~pointfree@c-174-62-81-78.hsd1.ca.comcast.net) joined #forth 22:12:42 Perhaps I could eliminate words like c!+ and just use c, to compile onto a counted string with the subspaces words { and } 22:55:59 I was thinking of maybe adding a subspaces stack to keep all the pointers when I move in and out of a level...but I kinda want to reduce stack proliferation/fragmentation. 23:21:38 --- quit: rgrinberg (Remote host closed the connection) 23:59:59 --- log: ended forth/16.10.30