00:00:00 --- log: started forth/18.01.26 00:12:37 --- join: Darkthird (~darksecon@84.243.212.208) joined #forth 00:13:40 --- quit: karswell (Ping timeout: 256 seconds) 01:06:10 newuser|14893: does that literally appear with hyphens like that? 01:07:42 the ANS document has basic usage of marker. could you post the code somewhere 02:03:54 it was :empty $" --maker-- maker --maker-- " evaluate ; 02:04:43 marker or maker? there's an r different there 02:05:07 :edit $" vim weave.fs " system ; :run $" weave.fs " included ; : ecr edit run ; 02:05:24 marker sorry my typo 02:07:40 https://www.youtube.com/watch?v=Q6FflPMHZP4 this was the tutorial (at 19min mark) 02:10:27 newuser|14893: that does not look right at all. put the whole file up somewhere 02:10:28 https://www.youtube.com/watch?v=mvrE2ZGe-rs&t=1735s 02:12:12 wait. do you even have source file are you painstakingly transcribing snippets from videos? 02:12:28 *source files or are you .. 02:12:30 I couldn't get the bit bucket to work... 02:13:04 Are there any good tutorials or videos for forth? 02:13:25 I found some of the books but most of the examples do not work with gforth or are very trivial. 02:13:41 it looks like your $ is really an S with bad video compression artifacts 02:13:52 ahh 02:14:16 anyway. i don't feel like sitting through videos right now 02:14:28 not sure of good recent tutorials :/ 02:14:39 its pretty dry, I was just there for the edit run loop he had going on. 02:15:33 oh right, starting forth has been updated for ANS 02:15:45 https://www.forth.com/starting-forth/ 02:16:38 could I ask a quick question, I am trying to find out if its possible to create a code block. What I want to do is create a bunch of CODE words that will output z80 assembler in forth from linux is that possible or does it have to be native assembly code? 02:18:36 --- part: Darkthird left #forth 02:18:36 you want to use something other than CODE for that, unless you have some special cross-compiling forth 02:20:09 yes what I want to do is generate a assembly listing, so that when I typed CLEARSCREEN in gforth it would look up the word and output the z80 assembly code to a portion of memory to be appended to a source file to save later. 02:22:00 so you want to strictly cross-compile and not run anything immediately on the build machine? 02:22:25 yes that right 02:23:45 like if it was for 6502, I would just say INITSCREEN and then it would place ldx #$00 stx $d021 stx $d020 in a text file/memory location. 02:24:16 that way i can use a external cross assembler to do the rest. 02:26:00 that gets hairy if you want immediate words. there are a few ways of dealing with that; all of them entail writing your own compiler 02:26:15 : INITSCREEN \t s" ldx #$00 \n \t stx $d021 \n\t stx $d020 \n" is what i was doing before but it seems an ugly solution I would prefer just to be able to use the opp codes. 02:26:52 ahh 02:27:01 then make a vocabulary with your own CODE that does the right thing 02:27:18 and your own : ,etc 02:28:03 ok cool so I should just stick with outputting the strings then formatting them as strings. 02:28:07 probably not ideal for a first project 02:29:10 I am able to write to the file, I was just hoping there was a way to do it with words, but if its going to be really difficult I better just stick with the strings. 02:29:55 Thanks very much for the advice, you saved me a lot of trouble. 02:30:36 there is is a way to do it with words. you just have to define them before you start outputting 02:31:42 could also do it with parsing words if you really wanted to, even if that isn't really traditional for code words (but could be reasonable if you're using an external assembler) 02:32:40 I think the parser would be less of a problem compared to using the immediate word 02:33:10 But that is still a pretty big job for a first project, even for a small instruction set. 02:33:38 you could have parsing words that just spit out the lines to the .asm file or whatever. 02:33:54 anyway, work through some tutorial and you should see roughly how to do it before too long 02:35:52 great thats given me some good direction. Cheers. 02:43:38 --- quit: newuser|14893 (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 02:48:24 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:10:39 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 05:11:12 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:12:19 --- quit: dddddd (Ping timeout: 240 seconds) 05:14:15 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 06:13:22 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 06:26:05 --- join: impomatic (~digital_w@host109-149-158-17.range109-149.btcentralplus.com) joined #forth 08:09:27 --- join: ncv_ (~neceve@90.194.21.108) joined #forth 08:09:27 --- quit: ncv_ (Changing host) 08:09:27 --- join: ncv_ (~neceve@unaffiliated/neceve) joined #forth 08:32:38 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 09:26:36 --- quit: impomatic (Quit: impomatic) 10:22:49 --- join: karswell (~user@cust125-dsl91-135-5.idnet.net) joined #forth 10:24:22 --- quit: Gromboli (Quit: Leaving) 10:41:51 --- join: dys (~dys@tmo-107-150.customers.d1-online.com) joined #forth 10:46:38 --- quit: dys (Ping timeout: 256 seconds) 10:47:06 --- join: dys (~dys@tmo-099-40.customers.d1-online.com) joined #forth 11:08:32 --- quit: dys (Ping timeout: 240 seconds) 11:12:09 --- join: dys (~dys@tmo-100-87.customers.d1-online.com) joined #forth 11:16:40 --- quit: dys (Ping timeout: 256 seconds) 11:44:22 --- quit: ncv_ (Ping timeout: 248 seconds) 11:49:04 --- join: ncv (~neceve@2a02:c7d:c5c9:a900:1ec6:932f:1b02:d27e) joined #forth 11:49:04 --- quit: ncv (Changing host) 11:49:04 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 11:51:16 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 12:03:43 --- join: dys (~dys@tmo-122-149.customers.d1-online.com) joined #forth 12:36:34 --- quit: ncv (Ping timeout: 256 seconds) 12:58:19 --- quit: Gromboli (Quit: Leaving) 13:28:54 --- quit: jedb (Ping timeout: 248 seconds) 14:36:50 --- quit: Darksecond_ (Read error: Connection reset by peer) 14:43:05 --- join: Darksecond (~darksecon@a82-94-53-70.adsl.xs4all.nl) joined #forth 14:44:34 --- join: ACE_Recliner (~ACE_Recli@96.75.44.74) joined #forth 16:15:50 --- quit: ACE_Recliner (Read error: Connection reset by peer) 17:06:57 --- quit: rpcope (Ping timeout: 240 seconds) 17:14:09 --- join: rpcope (~GOTZNC@162.245.217.4) joined #forth 21:03:10 --- join: jedb (~jedb@199.66.90.113) joined #forth 21:33:32 --- quit: dddddd (Remote host closed the connection) 21:38:57 --- join: Zarutian_PI2 (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 21:38:58 --- quit: Zarutian_PI (Read error: Connection reset by peer) 21:45:29 --- nick: Zarutian_PI2 -> Zarutian_PI 22:57:30 --- quit: lijero (Remote host closed the connection) 23:29:30 --- quit: dys (Ping timeout: 276 seconds) 23:37:17 --- join: dys (~dys@tmo-113-36.customers.d1-online.com) joined #forth 23:59:59 --- log: ended forth/18.01.26