00:00:00 --- log: started forth/06.04.24 00:23:05 --- part: imaginator left #forth 04:15:40 --- join: PoppaVic (n=pete@0-1pool66-51.nas22.chicago4.il.us.da.qwest.net) joined #forth 04:40:53 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 04:53:21 --- quit: tathi ("leaving") 05:32:32 humph 05:42:29 --- join: Cheery (i=Henri@a81-197-61-21.elisa-laajakaista.fi) joined #forth 05:52:08 --- join: madwork (n=foo@derby.metrics.com) joined #forth 06:02:44 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 06:18:39 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 06:21:29 --- quit: timlarson_ ("Leaving") 06:50:17 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 06:53:15 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 07:11:15 ok... Talk to me about a "stackframe" versus "variable/consts" or "locals" or "statics" 07:12:16 static/var/const take process-mem. 07:12:57 stackframe and locals don't, right? They persist for a "scope"? 07:35:22 --- quit: PoppaVic ("calls it a day - fuck it.") 07:55:32 I love my rpn calculator 07:57:31 --- join: Amanita_Virosa (n=jenni@adsl-69-154-178-250.dsl.hstntx.swbell.net) joined #forth 07:58:22 you love your rpn calc? 07:58:34 rpn is teh awesome. 08:00:09 it's so cool 08:40:28 hi 09:07:11 hi arke how are you? 09:21:33 doing alright 10:06:29 --- join: madwork_ (n=foo@derby.metrics.com) joined #forth 10:09:02 --- quit: madwork_ (Read error: 104 (Connection reset by peer)) 10:13:19 --- join: madwork_ (n=foo@derby.metrics.com) joined #forth 10:17:36 --- quit: madwork_ (Read error: 104 (Connection reset by peer)) 10:20:51 --- join: madwork_ (n=foo@derby.metrics.com) joined #forth 10:25:20 --- join: Ray_work (i=Raystm2@adsl-68-89-124-38.dsl.rcsntx.swbell.net) joined #forth 10:26:08 --- quit: Ray_work (Client Quit) 10:26:49 --- quit: madwork (Read error: 110 (Connection timed out)) 10:29:42 when I finish a first version of pix, I'll write an article for dotquote 10:30:14 i love my new forth, it's so twisted and perverse. 10:31:33 --- join: Ray_work (n=Raystm2@adsl-68-89-124-38.dsl.rcsntx.swbell.net) joined #forth 10:31:48 Amanita_Virosa, I'm interested in it :-) 10:32:00 what does it do different? 10:33:11 well, it's not a general-purpose forth, for one 10:33:14 it's an assembler. 10:33:31 the instruction emission functions are all provided in a forth dialect 10:33:36 a very *odd* forth dialect 10:33:46 can I have a look at it? 10:34:00 not sure how you'd go about that 10:34:13 it's not really ready for release at the moment 10:34:17 and it's part of a larger suite 10:37:02 a larger suite? 10:37:35 yes 10:37:42 it's part of a compiler toolchain 10:37:54 in this case, it's a multiplatform assembler. 10:38:10 hmm.. 10:38:31 how do you solve the problem of multiplatform assembler? 10:39:23 the tool is multiplatform, not the source it assembles. 10:39:39 it'll assemble the opcodes of any architecture you give it instruction tables for tho 10:40:32 and the problem is solved by making the assembler itself turing-complete. 10:41:39 which commands do you have for the assembler? 10:44:07 how do you mean, which commands? 10:47:07 how do you define such an instruction table for example? or how do you define sections and so on 10:48:02 well there's standard .section directives 10:48:05 for defining sections 10:48:10 instruction tables are much more complex 10:50:56 in what did you write that assembler? I assume in assembler 10:51:02 C. 10:51:09 oh, in C 10:51:26 so how did you implement the dictionary? 10:51:30 it's a full-featured assembler that writes to relocatable binaries 10:51:42 you're still trapped in the forth assembler paradigm. this is inside-out. 10:51:54 the forth is inside the assembler, not vice versa :P 10:52:25 eh? 10:52:43 the forth is inside the assembler?? 10:52:46 yep 10:52:59 i started by writing the typical backend of an object-file-writing assembler 10:53:01 what does that mean? 10:53:15 then i wrote a forth-like interpreted, 3-stack language 10:53:18 that drives that backend 10:53:34 and then glued a frontend onto that, which quite resembles the frontend of a typical assembler. 10:54:00 ok 10:54:16 it's not a "normal" FORTH by any definition 10:54:33 (neither is it a normal assembler, but it generates code successfully at this point) 11:42:21 --- quit: tathi ("leaving") 12:22:37 --- quit: Snoopy42 (Read error: 131 (Connection reset by peer)) 12:23:36 --- quit: Amanita_Virosa ("Wewpsies.") 12:23:55 --- join: Snoopy42 (i=snoopy_1@84.58.126.48) joined #forth 12:30:21 --- quit: Cheery ("Leaving") 12:35:05 hi 13:06:44 ho 13:10:49 --- nick: Raystm2 -> nanstm 14:32:20 --- quit: timlarson_ ("Leaving") 15:07:14 --- quit: virl (Remote closed the connection) 17:07:08 --- nick: nanstm -> Raystm2 17:17:10 --- join: verbatim (n=verb@130-127-44-5.chouse.resnet.clemson.edu) joined #forth 18:37:52 --- quit: uiuiuiu (Remote closed the connection) 18:37:53 --- join: uiuiuiu (i=ian@dslb-084-056-226-062.pools.arcor-ip.net) joined #forth 21:26:58 --- quit: verbatim ("Client exiting") 22:29:03 --- quit: JasonWoof ("off to bed") 22:50:44 --- join: Cheery (i=Henri@a81-197-61-21.elisa-laajakaista.fi) joined #forth 23:19:22 --- join: segher_ (n=segher@dslb-084-056-159-234.pools.arcor-ip.net) joined #forth 23:24:53 --- join: snowrichard (n=richard@adsl-69-155-177-154.dsl.lgvwtx.swbell.net) joined #forth 23:25:19 hello 23:26:11 --- quit: snowrichard (Client Quit) 23:28:00 --- quit: segher (Read error: 110 (Connection timed out)) 23:59:59 --- log: ended forth/06.04.24