00:00:00 --- log: started forth/19.01.05 00:02:43 --- quit: MrMobius (Ping timeout: 258 seconds) 00:02:43 --- nick: [1]MrMobius -> MrMobius 01:27:01 --- quit: proteusguy (Read error: Connection reset by peer) 01:27:18 --- join: proteusguy (~yaaic@2403:6200:88a6:329f:1de9:ef8a:1ae8:1089) joined #forth 01:27:18 --- mode: ChanServ set +v proteusguy 01:52:08 --- quit: pierpal (Read error: Connection reset by peer) 02:02:30 --- quit: ashirase (Ping timeout: 245 seconds) 02:03:44 --- join: proteusguy2 (~yaaic@2403:6200:88a6:329f:1de9:ef8a:1ae8:1089) joined #forth 02:03:44 --- quit: proteusguy (Read error: Connection reset by peer) 02:09:03 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:40:25 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 02:43:40 --- join: xek (~xek@apn-31-0-23-83.dynamic.gprs.plus.pl) joined #forth 02:57:07 --- quit: siraben (Read error: Connection reset by peer) 02:57:10 --- quit: bb010g (Read error: Connection reset by peer) 02:57:11 --- quit: jimt[m] (Read error: Connection reset by peer) 02:57:19 --- quit: Guest13462 (Read error: Connection reset by peer) 02:59:22 --- quit: rdrop-exit (Quit: Lost terminal) 03:00:07 --- quit: crc (Ping timeout: 246 seconds) 03:00:13 --- join: crc (crc@2a01:7e00::f03c:91ff:fe12:ac) joined #forth 03:01:53 --- join: proteusguy (~yaaic@2001:44c8:4447:e69d:1:1:aa87:f09f) joined #forth 03:01:53 --- mode: ChanServ set +v proteusguy 03:02:14 --- quit: proteus-ws (Remote host closed the connection) 03:04:27 --- quit: proteusguy2 (Ping timeout: 250 seconds) 03:10:47 --- join: bb010g (bb010gmatr@gateway/shell/matrix.org/x-xaypxmsgpwktitmf) joined #forth 03:13:34 --- join: `presiden (~presiden@unaffiliated/matematikaadit) joined #forth 03:17:27 --- quit: proteusguy (Read error: Connection reset by peer) 03:17:36 --- join: proteusguy (~yaaic@2403:6200:88a6:329f:1de9:ef8a:1ae8:1089) joined #forth 03:17:36 --- mode: ChanServ set +v proteusguy 03:24:53 --- join: proteusguy2 (~yaaic@2001:44c8:4447:e69d:1:1:aa87:f09f) joined #forth 03:28:15 --- quit: proteusguy (Ping timeout: 250 seconds) 03:41:12 --- join: Guest69125 (alexshpilk@gateway/shell/matrix.org/x-aonvxzwaqhhrkyqg) joined #forth 03:41:13 --- join: jimt[m] (jimtmatrix@gateway/shell/matrix.org/x-plfjjcvmagqmmamq) joined #forth 03:41:13 --- join: siraben (sirabenmat@gateway/shell/matrix.org/x-pelyjmpnksuxkzvt) joined #forth 03:47:30 --- quit: pierpal (Ping timeout: 245 seconds) 03:49:03 --- quit: proteusguy2 (Read error: Connection reset by peer) 03:49:16 --- join: proteusguy (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 03:49:16 --- mode: ChanServ set +v proteusguy 03:49:43 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 04:16:25 --- quit: proteusguy (Ping timeout: 246 seconds) 04:16:55 --- join: proteusguy (~proteus-g@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 04:16:55 --- mode: ChanServ set +v proteusguy 04:18:14 --- join: proteusguy2 (~yaaic@2001:44c8:4122:5b13:1:1:f2d4:1cb8) joined #forth 04:22:58 <`presiden> Is there exist online viewable list of ANS FORTH words list and it's explanation? 04:33:54 --- quit: proteusguy2 (Read error: Connection reset by peer) 04:34:09 --- join: proteusguy2 (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 04:36:36 --- join: proteusguy3 (~yaaic@2001:44c8:4122:5b13:1:1:f2d4:1cb8) joined #forth 04:36:58 --- join: proteusguy4 (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 04:37:04 --- quit: proteusguy2 (Read error: Connection reset by peer) 04:37:27 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 04:41:14 --- quit: proteusguy3 (Ping timeout: 264 seconds) 04:41:39 `presiden: https://forthworks.com/forth/standards/DPANS/DPANS.pdf 04:42:12 i think i need gdb backtrace viewer 04:52:33 <`presiden> corecode, thanks 04:57:55 <`presiden> I see a few mirror of the draft version too 04:58:04 <`presiden> http://lars.nocrew.org/dpans/dpans.htm 05:03:30 --- quit: Labu (Quit: WeeChat 2.0.1) 05:09:53 `presiden: are you implementing a forth? 05:20:42 <`presiden> corecode, not yet 05:22:11 `presiden: Just hang around a bit, you'll have your own forth in no time :D 05:22:53 <`presiden> :) 05:23:14 <`presiden> I alread have stacks and speak RPN :D 05:41:20 --- quit: pierpal (Quit: Poof) 05:41:39 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 05:51:51 `presiden: I'm a fan of https://forth-standard.org/standard/core 05:52:06 --- join: mark4 (~mark4@172.58.3.140) joined #forth 05:52:07 Has test cases too 05:52:39 I'd say stick with CORE words but don't worry about adding your own 05:53:08 When you get around to implementing 05:53:53 I recommended you implement it in assembly or if not, C 06:00:46 <`presiden> siraben, oh, that's nice 06:01:19 `presiden: any targets in mind? 06:01:27 It's easier than you might think to write a forth 06:03:34 any forth implemented in c is not forth 06:03:52 not unless you write a c compiler as an extension for your meta compiler 06:04:25 Yeah C may be too much baggage 06:04:33 learn assembler, code your primitives in assembler. write your forth kernel. write extensions to it in forth including an assembler and metacompiler 06:04:52 with c you need an FFI which is non trivial 06:05:03 `presiden: do you currently know any assembly? 06:06:14 asm is simple to learn too unless you try learning it from some MODERN tutorial. best book for x86 assembler tht has ever been written is STILL "The 8086 book, includes the 8088" 06:07:00 once you have 16 bit x86 mastered you already know 99.9999999999 percent of 32 bit 06:07:38 --- join: Labu (~Labu@labu.pck.nerim.net) joined #forth 06:08:24 you actually know more than 32 bit since all that segment switching stuff becomes unimportant 06:08:44 exactly 06:09:21 --- quit: Labu (Client Quit) 06:09:26 unless you are going to do pmode from scratch yourself in which case the segment registers become relevant again 06:11:02 --- join: Labu (~Labu@labu.pck.nerim.net) joined #forth 06:19:21 --- quit: Zarutian (Read error: Connection reset by peer) 06:19:43 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 06:46:55 <`presiden> siraben, ah, no, no concrete plan yet 06:47:39 --- quit: Labu (Quit: WeeChat 2.0.1) 06:50:06 mark4: just ordering that book now 06:50:15 you typed it with enough conviction, that I believe it 06:50:49 do I splurge and pay £100 for it new... 06:57:32 no 07:10:32 you're probably right 07:30:05 --- quit: xek (Ping timeout: 250 seconds) 07:30:16 --- join: gabc (~gabc@165.227.34.49) joined #forth 07:34:11 --- join: Kumool (~Khwerz@adsl-64-237-233-234.prtc.net) joined #forth 07:49:33 --- quit: mahmudov (Ping timeout: 250 seconds) 07:56:45 --- quit: pierpal (Quit: Poof) 07:57:02 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 08:04:04 --- join: mahmudov (~milisman@5.176.12.195) joined #forth 08:07:08 Real Men code their forth in direct hex, instead of assembler. 08:07:30 (the hairy-chested He-man will use panel-switches) 08:08:22 relevant xkcd https://www.xkcd.com/378/ 08:11:36 PoppaVic, my first "forthish" implementation was on a Hero-1 robot witha 6809, and I entered the whole thing in hex on the small alpha-numeric keyboard on top of it. :-) 08:12:20 proteusguy: I guess that counts then, not quite he-man, though ;-) 08:13:49 well the only alpha characters were those necessary to support hex a-f. 08:14:43 well, the panel-switches were binary - so.. You cheated ;-) 08:15:16 no panel switches by then.... :-) 08:16:18 I disagree, though: C is perfectly fine.. The biggest pain-in-the-dick is getting out from under it's ABI. 08:51:04 --- join: proteusguy2 (~yaaic@2001:44c8:4489:c1f3:1:1:a08e:a4a2) joined #forth 08:51:05 --- quit: proteusguy2 (Read error: Connection reset by peer) 08:51:05 --- quit: proteusguy4 (Read error: Connection reset by peer) 08:51:20 --- join: proteusguy2 (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 09:01:41 --- quit: proteusguy (Ping timeout: 258 seconds) 09:11:40 I am confused by something with forth. 09:11:50 I define a function, : field dup constant ; 09:11:58 a word, yes 09:11:59 then I say "field a" and it defines the field. 09:12:20 I don't understand how this works. Because 'a' is not on the stack yet. There is some silent macro thing going on. 09:12:30 no 09:12:38 `constant` parses the next word 09:12:43 in the input stream 09:12:44 aaah 09:12:53 how are you learning Forth? 09:12:54 constant does lookahead 09:12:58 see constant 09:12:59 : Constant 09:12:59 (Constant) , ; ok 09:12:59 see (constant) 09:12:59 : (Constant) 09:12:59 header reveal docon: cfa, ; ok 09:13:08 a bit like I play counterstrike - spray and pray 09:13:13 I'm quite unhappy with lookahead in forth. 09:13:15 (answer to how I am learning) 09:13:19 cratuki: perhaps you should read Starting Forth 09:13:20 I have a bluepill, and pforth 09:13:32 It's kinda ugly. I am thinking about not implementing lookahead at all. 09:13:35 I have that. I will go back to it. How many chapters do you recommend I should grind through/ 09:13:40 all of them 09:13:43 ugh 09:13:44 ok 09:13:45 except the one on blocks 09:13:45 thanks 09:14:02 you cannot exist with "lookahead", because that's how serial input works 09:14:08 john_cephalopoda: it's not really that ugly, it reads the TIB 09:14:31 no weird hacks or the like 09:15:05 I prefer how Retro uses string addresses on the stack for constants, but I don't see a mega problem with reading the input buffer 09:15:32 "string addresses on the stack" still uses lookahead. 09:15:36 with a regular Forth it makes sense - means you don't write ` S" WORD" : ` 09:15:42 PoppaVic: not in the same sense, not at all 09:15:49 wrong 09:15:54 it's not parsing the input buffer 09:16:57 where do you think the string came from? Stone tablets on the mount? 09:17:46 Considering "reading in a string" as lookahead I feel is wrong 09:20:16 --- join: mahtob (~milisman@37.155.4.93) joined #forth 09:21:01 --- quit: mahtob (Remote host closed the connection) 09:22:03 WilhelmVonWeiner: I'd kina prefer something like »S" SQUARE DUP *" :« over »: SQUARE DUP * ;« 09:22:42 i'm sorry but that's such an awful idea 09:23:04 * PoppaVic chortles 09:23:09 --- quit: mahmudov (Ping timeout: 258 seconds) 09:23:22 It looks weird and adds a bunch of completely unnecessary overhead 09:24:22 --- mode: ChanServ set +v crc 09:24:30 Idk... 09:24:32 --- mode: ChanServ set +o crc 09:24:35 I kinda get what you're saying 09:24:43 that syntax/approach in particular 09:24:44 Look-ahead is just strange imo. 09:25:12 you could use the kind of interpret/compile switching? 09:25:45 doing-stuff ] This will be in my word named bengis [ bengis 09:26:17 no that still wouldn't work because the interpreter dies at "bengis" the first time 09:26:30 i guess S" bengis" solves the problem 09:28:31 But S" also does look-ahead. 09:28:40 --- join: mahmutov (~milisman@unaffiliated/mahmutov) joined #forth 09:28:44 * PoppaVic chuckles 09:28:54 --- quit: Zarutian (Read error: Connection reset by peer) 09:29:16 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 09:30:34 ';' 32 '*' 'P' 'U' 'D' 32 'E' 'R' 'A' 'U' 'Q' 'S' : 09:31:08 ';' etc are defined words, which put the letter between the '' onto the stack. 09:31:21 Ergo, Retro prefixes/colorForth colours 09:31:26 * crc doesn't do lookahead 09:31:29 : Reads the stack letter for letter, compiles and does so until it reaches ';' 09:31:32 based crc 09:34:46 If I had : as a word it'd probably be used like [ code block ] 'wordname : 09:35:13 That's what I was going to type as an example, then I remembered how : already works lol 09:37:41 WilhelmVonWeiner: I may add this after the 2019.1 release 09:38:59 won't : be parsed as a prefix to nothing and break the matrix, though? 09:40:00 oh, it doesn't. Groovy 09:40:36 --- quit: Zarutian (Read error: Connection reset by peer) 09:41:17 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 09:42:00 Not if it's a single character name 09:42:13 I changed that a while back 09:42:41 did it simplify the code 09:43:41 :: const &class:word reclass ; 09:45:10 not in the kernel, but it made some things shorter and cleaner in the higher levels 10:24:29 --- quit: X-Scale (Ping timeout: 240 seconds) 10:27:12 --- quit: mark4 (Remote host closed the connection) 10:27:49 --- join: X-Scale (~ARM@31.22.201.16) joined #forth 10:37:39 ok, now i can print the return stack from gdb 10:37:57 Yay! 10:52:50 not sure how to implement "next" 10:54:47 corecode: That one has something on "next": http://www.bradrodriguez.com/papers/moving1.htm 10:54:59 Not sure if it is the same as the ANS next though 10:57:56 --- quit: pierpal (Read error: Connection reset by peer) 10:58:11 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 10:58:21 NEXT isn't ans afaik 10:58:46 ANS is application words 10:59:50 i mean, gdb next 11:00:13 --- quit: gravicappa (Ping timeout: 250 seconds) 11:01:09 which needs to consider EXIT, BRANCH, 0BRANCH, and words that return more 11:02:49 --- quit: pierpal (Ping timeout: 258 seconds) 11:05:33 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 11:09:29 --- quit: pierpal (Ping timeout: 240 seconds) 11:27:18 --- quit: dave0 (Quit: dave's not here) 11:43:01 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 11:46:26 --- quit: mahmutov (Ping timeout: 268 seconds) 11:49:35 --- quit: pierpal (Ping timeout: 258 seconds) 11:55:41 --- quit: tabemann (Ping timeout: 250 seconds) 11:55:49 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 11:58:59 --- quit: pierpal (Read error: Connection reset by peer) 12:06:38 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 12:09:27 --- quit: pierpal (Read error: Connection reset by peer) 12:11:59 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 12:14:24 --- join: mahmudov (~milisman@37.155.4.93) joined #forth 12:18:22 --- quit: pierpal (Ping timeout: 246 seconds) 12:24:20 i've never liked the .s and ." thing for strings - in my approach it's simply $ with optional quotes or escapes - and added a printf so you can go: $ "world" $ "hello %s" printf (with evaluation being from left to right on the stack - ie: 1 2 3 $ "%d %d %d" printf gives "1 2 3") 12:24:51 think that's kinda nice myself 12:34:35 I use s:format for that: 12:35:00 'world 'hello_%s s:format s:put 12:35:04 #1 #2 #3 '%n_%n_%n s:format s:put 12:38:47 nicer :) - but no spaces or other chars by way of escape? and special case for numerics? 12:39:04 _ is replaced by space 12:39:18 yeah - but then then how do you do an _? 12:39:31 escape with \_ or not possible? 12:40:50 https://forthworks.com/share/b209b8ed5fa7272e914652cf4de98fee 12:40:54 yes, \_ 12:41:50 my forth is *very* non-standard. It uses prefixes to guide the interpreter in processing input on a token by token basis 12:42:18 yeah - that makes sense 12:42:37 # prefix is used to convert a token into a number, ' to process as a string, : to start a definition, & to get a pointer, etc 12:43:08 there's no way to parse ahead, so I can't have things like ." or s" 12:43:39 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 12:43:40 k - i found the $ with a space following works best for me - shells don't nuke it, so you can pass it as a command line argument 12:44:12 that maybe a poor reason in the grand scheme of things, but it works for me :) 12:44:20 (and prefixes are just words in the dictionary following a special naming scheme, so they can be added or replaced as desired) 12:46:42 nice - i was considering a set of words which are specified as regex's :) - heavy but could be useful for specifics - never tried it though 12:48:14 --- quit: pierpal (Ping timeout: 258 seconds) 12:49:19 --- join: proteusguy (~proteus-g@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 12:49:19 --- mode: ChanServ set +v proteusguy 12:49:47 * crc wants to write a regex implementation some day 12:50:59 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 12:51:35 specifically, in my video 'language' i have a syntax which is pretty much described as: [ [ name=value ]* [ filter: [ name=value ]* ]* - urls being files, http, ftp or whatever - filter:.* and even http:.* kinda stuff would be nice (mebbe :)) 12:52:58 nice thing about stack based languages is that they're kinda sweet for specifying graphs 12:55:31 --- quit: pierpal (Ping timeout: 258 seconds) 12:56:12 the_cuckoo: look up colorForth 12:57:21 hmm - i've come across it before, but didn't look into specifics 12:57:33 Should do so 12:59:10 so much stuff, so little time :) 13:00:50 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 13:03:47 --- quit: pierpal (Read error: Connection reset by peer) 13:07:15 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 13:11:15 --- quit: moony (Quit: Bye!) 13:11:29 --- quit: pierpal (Ping timeout: 240 seconds) 13:16:08 --- join: moony (moony@hellomouse/dev/moony) joined #forth 13:19:59 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 13:26:34 --- quit: pierpal (Ping timeout: 258 seconds) 13:31:49 --- quit: moony (Quit: Bye!) 13:35:17 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 13:36:29 --- join: moony (moony@hellomouse/dev/moony) joined #forth 13:42:22 --- quit: pierpal (Ping timeout: 268 seconds) 13:46:02 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 13:50:09 --- quit: pierpal (Ping timeout: 240 seconds) 14:00:20 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 14:07:13 --- quit: pierpal (Ping timeout: 246 seconds) 14:15:59 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 14:22:32 --- quit: pierpal (Ping timeout: 258 seconds) 14:24:47 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 14:29:10 --- quit: pierpal (Ping timeout: 245 seconds) 14:58:10 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 15:00:17 --- join: tabemann (~tabemann@2602:30a:c0d3:1890:7d04:1e92:6395:7db) joined #forth 15:07:58 looking at old forth conference proceedings 15:08:30 Forth information is so wide-spread and oddly distributed 15:11:52 I suspect FIDONET and other CBBS systems that carried mail and articles between sites might have helped. 15:13:00 * Zarutian now wonders if any CBBSes were Forth based as it is pretty easy to make a multi-user/multi-tasked/multi-programmed Forth 15:13:32 you know, so the OPs could have used his machine to do stuff even when someone phoned into it. 15:17:31 back 15:17:54 wb, tabemann 15:18:02 hey guys 15:33:02 --- nick: FatalNIX -> bhodgins 16:10:31 --- quit: john_cephalopoda (Ping timeout: 250 seconds) 16:12:21 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:18:16 --- quit: pierpal (Ping timeout: 250 seconds) 16:18:27 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 17:03:28 --- quit: pierpal (Read error: Connection reset by peer) 17:22:37 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 17:24:26 --- quit: tabemann (Ping timeout: 264 seconds) 17:24:26 --- quit: pierpal (Read error: Connection reset by peer) 17:31:04 yey 17:31:17 my forth finally can compile words and execute them 17:31:40 Yay! 17:32:26 The "best" forth stuff is still buried in the FORML stuff, and frankly, I refuse to spend a penny for such dated/antiquated info. 17:34:02 https://github.com/corecode/forth 17:34:11 in case somebody wants to explore 17:36:09 corecode: your dictionary is still a map and you don't seem to have any kind of threading model 17:36:39 On the upside, it has a Makefile. It went downhill from there ;-) 17:37:16 I wouldn't say that, it's the approach I'd expect from someone I imagine hasn't implemented or read a book on implementing a forth before 17:37:45 WilhelmVonWeiner: my dictionary is not a map 17:38:05 why wouldn't i use a makefile? 17:38:32 WilhelmVonWeiner: i think you're talking about the metacompiler? 17:38:53 `class Forth: ... self.dict = {}` in Forth.py 17:39:12 the metacompiler is not meant to be a full forth, it just compiles the forth kernel 17:39:21 that is forth-asm.py? 17:39:41 as soon as I saw .py, and x86.s - I ran screaming ;-) 17:40:11 oh forth.py is old and needs to die 17:41:47 oh I see what you're doing now 17:41:51 after seeing x86.fs 17:41:54 cool 17:42:07 i tried to write the forth in forth 17:42:12 as one should 17:42:18 but to bootstrap myself, i used python 17:42:24 i ended up replicating a lot 17:42:45 but then i don't have to rely on gforth being installed and me figuring out how to do all of that 17:42:58 in the end, i want to integrate this into an existing C application 17:43:30 you could've used pforth I suppose 17:43:44 instead of writing one? 17:43:49 yeah 17:43:53 yea but what fun is that 17:43:57 --- quit: proteusguy2 (Read error: Connection reset by peer) 17:44:08 well, means you get to use Forth as opposed to meta-use Forth sooner 17:44:16 yea 17:44:28 but now i already trained writing forth 17:45:40 --- join: proteusguy2 (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 17:45:57 also pforth is much larger 17:47:05 well, it comes with a ton of ANS words you can leave out 17:47:16 and multiple tasks etc 17:52:14 doesn't build for me (I had to assemble forth-x86.o by hand, as the ASFLAGS weren't being picked up), but it's complaining about a missing main.o 17:52:26 oh 17:52:37 corecode: crc is a FreeBSD user 17:52:44 --- quit: proteusguy2 (Ping timeout: 268 seconds) 17:52:53 it might hold some relevance 17:52:55 what's wrong with ASFLAGS? 17:53:26 no canned rule that uses ASFLAGS? 17:53:54 crc: Out of curiosity are you able to install Guile for your operating system and run "make build" for https://github.com/siraben/zkeme80 ? 17:54:03 WilhelmVonWeiner: true enough, though I may be switching my dev system over to OpenBSD soon. 17:54:04 It should be reproducible because I wrote it only in Scheme 17:54:06 so right now it only evaluates the first argument, and anything wrong will crash 17:54:22 crc: OpenBSD is awesome. 17:54:29 --- quit: proteusguy (Ping timeout: 246 seconds) 17:54:48 i got tired porting drivers for new hardware 17:54:52 so i switched to linux 17:54:54 And ports are so good, it's nice to be able to install GIMP and all it's dependencies and remove it all perfectly clean without any stress after editing some image 17:55:33 crc: let me know if it works or not 17:58:11 --- join: proteusguy (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 17:58:11 --- mode: ChanServ set +v proteusguy 17:58:18 siraben: nope: https://forthworks.com/share/1cc451dd5be108144ae23d2998dfb3af 17:58:29 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 17:58:39 crc: run "make build" 17:58:50 make assumes you have the emulator built and aliased to tilem2 18:01:03 still fails: https://forthworks.com/share/3254b31d0ac897794cd26d076723a758 18:02:19 Huh how are you installing guile? 18:02:23 WilhelmVonWeiner: I really only need an assembler, C compiler, Fossil, inetd, and Retro :) 18:03:03 Is it avaliable from a package manager? 18:03:12 comes with fvwm, xterm, mg, vi 18:03:18 everything you need to edit and hack 18:03:20 siraben: yes: pkg install guile 18:03:30 and then ofc c development tools 18:05:00 WilhelmVonWeiner: I set up a VPS running it last night and will copy a mirror of my home dir to it over the next week 18:06:14 crc: could you change (ice-9 binary-ports) to (rnrs io ports) 18:06:18 in assembler.scm? 18:07:15 What version of Guile is packaged for your OS? 18:07:30 1.8.8 18:08:33 https://forthworks.com/share/64bccc217b6afdfa364634d25820754f after making that change 18:09:24 Must be an old version thing 18:09:26 I'm on 2.2.3 18:11:00 1.8.8 was released in 2010, hm. 18:11:40 I'll try to build 2.2.3 from source 18:12:00 crc: which package manager is this? 18:12:08 Seems odd that Guile is so outdated 18:12:11 pkg is part of FreeBSD 18:12:15 it's a BSD 18:12:29 most ports are somewhat outdated 18:12:35 uses the FreeBSD Ports packages 18:12:42 https://www.freebsd.org/ports/scheme.html 18:12:43 Ah 18:12:56 crc: try installing the guile2 package? 18:14:02 will do 18:19:26 and that package is broken due to freebsd not having libdl.so (can't even launch guile) 18:25:06 ld.so contains the functionality of libdl.so 18:25:12 trying to build from source now 18:25:45 --- join: tabemann (~tabemann@2602:30a:c0d3:1890:7d04:1e92:6395:7db) joined #forth 18:25:57 crc: ok, hope it works. 18:26:26 hey guys 18:27:21 hi tabemann 18:29:30 hello 18:38:51 corecode: iirc, on freebsd, libc has dummy functions for dlopen, dlsym, etc, and ld.so patches these at load time to the actual functions 18:44:18 No luck. Building guile2 fails with: https://forthworks.com/share/6f3c357a63f063316045946d127e1d80 18:44:53 bummer, oh well. 18:45:12 hence why we need reproducible builds and environments 18:46:05 gnuc: sticks to kids ;-) 18:46:46 * siraben posted a file: zkeme80.rom (1024KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/CtEMevYsBgFoGXKVYMhrYbOc > 18:46:48 crc: here's the rom 18:47:02 if you want to try it out the easiest way to do so is https://www.cemetech.net/projects/jstified/ 18:47:09 and clicking on the "ROM" tab 18:47:19 currently there isn't much so when the calculator boots just hit spacebar 18:49:39 --- quit: pierpal (Quit: Poof) 18:50:00 --- join: pierpal (~pierpal@95.239.223.85) joined #forth 18:53:50 --- quit: tabemann (Ping timeout: 264 seconds) 18:56:02 Tests run fine, it crashes when I try to use the repl 18:56:27 Ah "crash", basically it shuts down 18:56:35 I haven't implemented the L part of the REPL 18:56:37 lol 18:56:58 I need to fix that, not sure what's holding me back in designing the REPL 18:57:05 No worries, the rest looks good 18:57:12 That's good 18:58:04 --- quit: proteusguy (Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org) 18:58:35 --- join: proteusguy (~proteus-g@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 18:58:35 --- mode: ChanServ set +v proteusguy 18:59:02 --- nick: proteusguy -> proteusguy-satri 18:59:24 --- join: proteusguy (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 18:59:24 --- mode: ChanServ set +v proteusguy 19:03:28 --- join: tabemann (~tabemann@2602:30a:c0d3:1890:7d04:1e92:6395:7db) joined #forth 19:21:31 --- join: rdrop-exit (~markwilli@112.201.166.158) joined #forth 19:36:30 --- quit: rdrop-exit (Quit: Lost terminal) 19:47:43 --- join: dave0 (~dave0@47.44-27-211.dynamic.dsl.syd.iprimus.net.au) joined #forth 19:48:33 hi 20:02:08 --- quit: tabemann (Ping timeout: 268 seconds) 20:12:48 --- join: proteusguy2 (~yaaic@182.232.82.157) joined #forth 20:13:18 --- join: rdrop-exit (~markwilli@112.201.166.158) joined #forth 20:13:18 --- quit: proteusguy2 (Read error: Connection reset by peer) 20:13:42 --- quit: proteusguy (Ping timeout: 244 seconds) 20:14:38 --- join: proteusguy (~yaaic@2001:44c8:4285:5500:1:2:f5c6:3f2f) joined #forth 20:14:38 --- mode: ChanServ set +v proteusguy 20:14:48 Hello Forthwrights :) 20:18:44 <`presiden> sounds similar to forthnite 20:40:57 --- quit: rdrop-exit (Quit: Lost terminal) 21:00:47 --- join: gravicappa (~gravicapp@h109-187-254-198.dyn.bashtel.ru) joined #forth 22:07:57 --- join: tabemann (~tabemann@2602:30a:c0d3:1890:7d04:1e92:6395:7db) joined #forth 22:10:04 --- quit: proteusguy (Read error: Connection reset by peer) 22:10:19 --- join: proteusguy (~yaaic@cm-58-10-154-246.revip7.asianet.co.th) joined #forth 22:10:19 --- mode: ChanServ set +v proteusguy 22:22:20 --- quit: Kumool (Quit: EXIT) 22:43:05 --- quit: PoppaVic (Ping timeout: 268 seconds) 22:47:16 --- quit: dddddd (Remote host closed the connection) 22:55:37 --- join: PoppaVic (~PoppaVic@unaffiliated/poppavic) joined #forth 23:37:07 --- join: xek (~xek@apn-31-0-23-83.dynamic.gprs.plus.pl) joined #forth 23:57:49 --- quit: pierpal (Remote host closed the connection) 23:59:59 --- log: ended forth/19.01.05