00:00:00 --- log: started forth/15.08.06 00:06:04 --- quit: proteusdroid_ (Read error: Connection reset by peer) 00:15:39 what should cold do? 00:23:01 --- quit: ASau (Ping timeout: 256 seconds) 00:31:42 --- nick: xyh -> little-enchantin 00:32:04 --- nick: little-enchantin -> little-demon-fox 00:32:24 hi 00:32:41 #forth talk to me!!! 00:34:25 --- quit: proteusguy (Ping timeout: 260 seconds) 00:52:46 --- join: proteusguy (~proteusgu@ppp-110-168-229-208.revip5.asianet.co.th) joined #forth 00:52:46 --- mode: ChanServ set +v proteusguy 01:20:12 --- quit: Keshl (Read error: Connection reset by peer) 01:20:20 --- join: Keshl (~Purple@24.115.181.94.res-cmts.gld.ptd.net) joined #forth 01:21:28 --- nick: Keshl -> Keshi 01:21:40 --- nick: Keshi -> Keshl 02:10:53 --- quit: FireFly (Ping timeout: 244 seconds) 02:27:43 --- join: atommann (~atommann@58.251.2.94) joined #forth 02:29:37 https://codecombat.com/play guys check this , tech programming using dungeon like game 02:30:19 i think forth is more suitable in such case, since it looks like real curse 02:30:22 --- quit: TodPunk (Read error: Connection reset by peer) 02:47:32 --- nick: little-demon-fox -> xyh 03:09:15 --- quit: atommann (Quit: Leaving) 03:49:58 --- join: true-grue (~grue@95-27-152-30.broadband.corbina.ru) joined #forth 04:08:19 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 04:34:55 yunfan_: see https://github.com/JohnEarnest/Mako/tree/master/games/Warrior2 04:38:09 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 06:25:06 hello. I'm going through the starting forth book, and at chapter 3 I'm slightly confused at the "how forth uses the disk" bit. I'm assuming this sort of thing has changed a lot since the book was written. pforth doesn't have a "use" word, for instance. Is there a brief overview anywhere of e.g. how to go through "starting forth" using gforth? 06:25:54 I really enjoy Brodie's writing (I decided to read starting forth having read most of thinking forth), and I don't want to switch track and start ploughing through the gforth info pages 06:30:38 ksj: you could maybe try getting an old forth and running it under dosbox 06:31:06 i don't really know of a modern block-based forth. 06:31:19 (that doesn't mean there isn't one) 06:31:43 but also you can probably just skim through that part 06:34:16 tangentstorm: ok, so blocks aren't really relevant to modern forth then? 06:34:27 I was trying to wrap my head around what exactly is going on 06:34:32 ksj: I just ignored the old part [to know there is an old way of using disk, and maybe come back to it when you find you need it] 06:35:21 yeah, thanks, I'm happy to skip it if it's really not necessary, I just generally avoid skipping parts of texts I don't understand because it comes back to bite you later 06:35:50 also, good to know you guys are here and respond quickly. I kind of assumed this channel would be fairly dead 06:36:00 yeah... colorforth still uses blocks, and you might find that sort of thing if you're doing embedded work (not sure) but all the big forths support some kind of file wordset 06:36:14 we're all ghosts. :) 06:37:52 --- quit: proteusguy (Read error: Connection reset by peer) 06:39:43 does anyone use colorforth apart from chuck moore? I mean, it seems kind of cool, but I haven't had a machine with a floppy disk for a lonnnnng time 06:41:35 the one on colorforth.com is way old 06:41:42 the latest work is all at greenarrays.com 06:41:57 http://www.greenarraychips.com/ sorry. 06:42:34 it's called arrayforth, but it's colorforth 06:48:05 --- join: kumul (~mool@adsl-72-50-86-38.prtc.net) joined #forth 06:49:09 --- quit: karswell (Remote host closed the connection) 06:49:12 ksj; [blocks] consider a partition that has no fs on it. that's what is meant by forth blocks; the blocks can also simulated in ram only, no alternate storage. 06:49:50 Quiznos: https://github.com/kt97679/relf/blob/master/kernel.4#L1286 06:49:50 Stuff about Forth startup: http://www.jimbrooks.org/programming/forth/forthInternals.php 06:51:23 --- quit: irsol (Ping timeout: 246 seconds) 06:52:46 ok 06:53:51 --- join: proteusguy (~proteusgu@ppp-110-168-229-141.revip5.asianet.co.th) joined #forth 06:53:51 --- mode: ChanServ set +v proteusguy 06:55:04 --- join: bedah (~bedah@dyndsl-091-096-195-099.ewe-ip-backbone.de) joined #forth 06:55:53 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 07:11:58 --- join: FireFly (~firefly@firefly.xen.prgmr.com) joined #forth 07:14:19 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 07:18:29 --- quit: FireFly (Changing host) 07:18:29 --- join: FireFly (~firefly@oftn/member/FireFly) joined #forth 07:57:15 --- join: impomatic (~impomatic@31.185.136.135) joined #forth 08:09:28 --- quit: kumul (Ping timeout: 265 seconds) 08:15:30 --- quit: vsg1990 (Read error: Connection reset by peer) 08:18:40 --- join: kumul (~mool@adsl-72-50-86-38.prtc.net) joined #forth 08:23:13 --- join: kumool (~mool@adsl-64-237-237-133.prtc.net) joined #forth 08:25:53 --- quit: kumul (Ping timeout: 246 seconds) 09:49:48 --- quit: kumool (Ping timeout: 250 seconds) 10:06:53 --- join: kumul (~mool@adsl-64-237-237-133.prtc.net) joined #forth 10:14:46 --- join: kumool (~mool@adsl-72-50-84-102.prtc.net) joined #forth 10:17:40 --- quit: kumul (Ping timeout: 260 seconds) 10:21:09 --- quit: darkf (Quit: Leaving) 11:00:28 --- quit: workp (Quit: leaving) 11:03:55 --- join: ASau (~user@46.114.41.237) joined #forth 11:06:17 --- join: fantazo (~fantazo@089144225031.atnat0034.highway.a1.net) joined #forth 11:11:40 --- join: beretta (~beretta@cpe-65-185-42-203.columbus.res.rr.com) joined #forth 11:17:15 --- nick: xyh -> little-demon-fox 11:21:11 --- nick: little-demon-fox -> little-night-fox 11:25:47 --- part: twinshadow left #forth 11:29:49 --- quit: little-night-fox (Remote host closed the connection) 11:39:14 --- quit: joneshf-laptop (Ping timeout: 265 seconds) 11:47:29 --- quit: Quiznos (Quit: leaving) 11:48:05 --- join: Quiznos (1000@c-73-28-150-210.hsd1.fl.comcast.net) joined #forth 12:03:41 --- quit: irsol (Ping timeout: 260 seconds) 12:11:08 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 12:14:03 . 12:25:48 --- quit: fantazo (Ping timeout: 250 seconds) 12:43:17 --- join: fantazo (~fantazo@089144197125.atnat0006.highway.a1.net) joined #forth 12:45:21 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 12:45:24 --- quit: ASau (Remote host closed the connection) 12:47:53 --- join: ASau (~user@46.114.41.237) joined #forth 12:48:58 --- join: Mat4 (~claude@ip5b40b95e.dynamic.kabel-deutschland.de) joined #forth 12:48:59 hello 12:49:57 --- quit: ASau (Remote host closed the connection) 12:50:54 --- join: ASau (~user@46.114.41.237) joined #forth 12:53:17 --- quit: fantazo (Ping timeout: 245 seconds) 12:56:11 Mat4: Hello. 12:57:16 Quiznos: For FIG Forth 'cold' should just reinitialize the forth environment to there, implementation dependent final state if this was your question 12:57:19 hi DKordic 12:58:31 a typical FIG Forth execute COLD, WARM and ABORT after starting the VM 13:02:32 --- join: bedah2 (~bedah@dyndsl-091-096-195-099.ewe-ip-backbone.de) joined #forth 13:03:50 Mat4: hi; ya, i was just lookin to stir up a chat, but also looking for a reminder. 13:03:56 ya 13:04:27 --- quit: bedah (Ping timeout: 240 seconds) 13:06:27 --- quit: bedah2 (Client Quit) 13:06:37 --- join: bedah (~bedah@dyndsl-091-096-195-099.ewe-ip-backbone.de) joined #forth 13:10:10 --- join: kumul (~mool@adsl-72-50-84-102.prtc.net) joined #forth 13:11:12 --- quit: defanor (Ping timeout: 245 seconds) 13:12:27 --- quit: JohnMarkM (Ping timeout: 245 seconds) 13:12:45 --- quit: kumool (Ping timeout: 260 seconds) 13:12:50 --- join: JohnMarkM (~johnmark@24.1.223.32) joined #forth 13:13:26 yester I read up some posts about closures and structure handling 13:14:48 --- join: defanor (~defanor@cupcake.uberspace.net) joined #forth 13:16:52 for me it is interesting that structure requests seem to follow logic behaviour of Algol oriented languages in demanding formatted arrays though concretisation of an uniform data abstraction 8the structure) 13:18:38 where in Forth it is possible to represent concrete data formats simply by specific words 13:19:12 "concrete" 13:19:33 I always love these sorts of terms when talking about stuff that is all abstraction 13:19:42 "I had to apply the patch by hand" etc 13:20:16 https://xkcd.com/378/ 13:21:20 it's prose in forth. 13:26:39 my point is that structures can be of no advantage implemented in languages like Forth because all format specifications which relate on the need for compound types in Algol languages (like structures) result from limitations of there type systems (in my interpretation) 13:28:20 I think because Forth is a quite different language handling data formats need to be represented differently to be effective 13:29:27 so why not simply define words for handling different data formats (there can be extended at demand and factored in the same way as structure declarations in Algol languages at demand) ? 13:31:40 sorry, bad english translation 13:36:29 just wondering 13:37:03 that is what writing a DSL is all about; Leo called them 'lexicons' 13:37:10 fig called them vocabulries 13:37:22 dsl -. domain specific languages 13:37:34 al meaning the same thing 13:41:14 --- join: impomatic_ (~digital_w@31.185.136.135) joined #forth 13:44:41 yes 13:46:14 and the most well-known DSLs are lisp and forth. 13:46:30 polar oppossites to each other and each as powerful as the other. 13:51:46 I think lisp has the advantage of equality between code and data and the disadvantage of greater complexity compared to Forth. It is also easier to optimize Forth definations 13:52:26 each has its own pros/cons 13:54:34 for my current project I will add definations for altering the source code at edit stage (for programmable generation of interfaces for example) 13:55:48 so I can program the generation of programs without the limitations of text processing macros 14:02:10 k 14:10:36 --- part: impomatic_ left #forth 14:20:51 --- quit: bedah (Remote host closed the connection) 14:41:03 Mat4: you there? 14:41:54 Mat4: you're taling about meta-programming now. excellent!!! 14:43:50 tal/talk 14:47:12 yes, programming 14:48:35 --- quit: kumul (Quit: Leaving) 15:04:33 --- quit: true-grue (Read error: Connection reset by peer) 15:21:52 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 15:36:08 --- join: kumul (~mool@adsl-72-50-86-38.prtc.net) joined #forth 16:10:31 ciao 16:10:33 --- quit: Mat4 (Quit: Verlassend) 18:01:13 --- quit: kumul (Ping timeout: 255 seconds) 18:22:14 --- join: atommann (~atommann@58.251.2.94) joined #forth 20:04:49 --- quit: atommann (Ping timeout: 250 seconds) 20:17:42 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 20:20:44 --- quit: malyn (Remote host closed the connection) 20:22:43 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 20:22:46 --- quit: malyn (Remote host closed the connection) 20:23:06 --- quit: vsg1990 (Read error: Connection reset by peer) 20:23:32 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 20:30:14 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 20:48:32 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 21:20:42 --- join: zhiayang (~zhiayang@bb219-74-68-213.singnet.com.sg) joined #forth 21:21:57 --- join: atommann (~atommann@58.251.2.94) joined #forth 21:25:28 --- quit: vsg1990 (Quit: Leaving) 21:47:02 --- join: xyh (~xyh@14.150.214.16) joined #forth 22:07:20 --- join: kumul (~mool@adsl-72-50-86-38.prtc.net) joined #forth 22:42:47 --- quit: atommann (Ping timeout: 246 seconds) 22:52:27 --- quit: kumul (Ping timeout: 245 seconds) 23:19:49 --- quit: ASau (Ping timeout: 255 seconds) 23:31:56 --- join: atommann (~atommann@58.251.2.94) joined #forth 23:59:59 --- log: ended forth/15.08.06