00:00:00 --- log: started forth/21.07.16 01:06:21 --- join: Glider_IRC__ joined #forth 01:09:12 --- quit: Glider_IRC_ (Ping timeout: 120 seconds) 06:47:50 i think that i might have a brain problem 06:48:12 three of the last four bugs i wrote at work were inverted logic 06:48:37 "if" when it should have been an "if not", or ">" when it should have been "<=", etc. 06:59:26 All work and no play makes you forget words how work. 07:34:55 are you saying that if this keeps up i'm going to go on a murderous rampage with a fire axe against my own family in a spooky hotel during a blizzard? 07:35:26 i better take some time off, then. i wonder if my manager will accept that as a good reason 07:37:42 He'd better. 07:37:43 Яedrum 09:54:12 what are some forthlikes besides retro and mako that run on virtual machines with small instruction sets? 09:54:54 or i guess where else can i see someone's take on a core set of words that make up a forthlike? 09:55:08 uxn? 09:55:12 (oh i already have f-18 from greenarrays) 09:55:12 colorforth? 09:55:55 uxn is a stack vm 09:56:52 ah googling that lead to https://github.com/jinhanada/arkam as well 10:20:36 tangentstorm: A lot of languages are like that, JVM, Lua, many old BASICs 10:20:51 The B implementation on the PDP-11 10:21:58 yeah. i'm interested mostly in the ones with very small instruction sets 10:22:48 mostly just curious which opcodes the designers picked to be their 'axioms' 10:23:06 i suppose it doesn't really matter :) 10:29:51 i'm toying around with a vm idea that works like the utf-8 encoding scheme, where any asci letter just writes a byte to ram, and any valid utf-8 sequence does the same for multi-byte characters. 10:30:29 which leaves something like 64 bytes available to hold other instructions. 10:30:47 64 opcodes i mean. 11:16:19 im assuming an address register then 11:20:32 yeah, there's a read register and a write register like in colorforth 11:21:26 f18 has two registers that can be both read and written 11:21:34 https://github.com/sabren/b4/blob/master/j/b4.ijs <- j, so i don't know how readable this is :( 11:21:55 i kinda think that if you're going for a forth, it almost doesn't matter what your VM looks like... forth is the vm. 11:22:10 you just need to pick something to host it. 11:22:32 I also feel this way 11:24:07 veltas: o/ saw you on HN 11:24:29 wow, folks actuslly writing j 11:24:33 didnt know that happened 11:25:13 :D i write k at work, and j for fun. (and occasionally for a youtube channel) 11:27:37 oh wow 11:27:48 how'd you land that job? 11:32:06 my old boss posted to the apl/j/k subreddit. 11:32:35 haha 11:33:24 well, i mean he wasn't my old boss at the time. but i met him on there and it worked out. :) 11:36:33 i don't know if we're hiring at the moment (i'm on paternity leave) but i wrote this about it a few months ago when we were: https://www.linkedin.com/pulse/want-work-k-1010data-michal-wallace/ 11:37:22 the guy that made mako used to work there too, and found it through the same reddit post :) 12:14:27 Hello, this might be a rather niche question, but is anyone aware of a Forth that runs on J2ME/Java ME? https://stackoverflow.com/questions/1889034/what-programming-languages-target-j2me/1891023#1891023 12:25:47 --- quit: iv4nshm4k0v (Client exited) 12:26:18 --- join: iv4nshm4k0v joined #forth 12:27:46 hendursaga: google turns this up: https://pdroms.de/sunmicrosystems-j2me/mid4th-v1-44-j2me-application 12:32:57 huh, missed that one 13:06:37 --- join: Glider_IRC_ joined #forth 13:08:56 --- quit: Glider_IRC__ (Ping timeout: 120 seconds) 14:58:06 retro10 had an implementation that ran on j2me. 15:31:09 --- quit: a3f (Ping timeout: 120 seconds) 15:32:22 --- join: a3f joined #forth 15:33:02 --- quit: Vedran (Connection closed) 15:33:10 --- join: Vedran joined #forth 23:24:16 maw 23:59:59 --- log: ended forth/21.07.16