00:00:00 --- log: started retro/11.11.09
01:50:27 --- join: C-Keen (cckeen@pestilenz.org) joined #retro
02:18:14 <C-Keen> I am currently reading: http://retroforth.org/docs/html/An_Introduction_to_Retro.html and in the examples there is 'putn' inserted in the code but not explained. Is that some kind of markup leftover?
05:31:06 <scj> are there any plans on bringing back the net' vocab?
06:19:39 --- join: Kumul (~Kumul@adsl-64-237-225-143.prtc.net) joined #retro
08:46:11 <retro_commits> vm: html5: minor ui tweaks to settings pane in mobile view : http://rx-core.org/rx.fossil/info/9a8d5e35dfd7fe46f8c1f9654f799038ff7e92fb
08:46:28 <retro_commits> vm: html5: update to latest image+libraries : http://rx-core.org/rx.fossil/info/155a1f396ca3340cd0a29540d9e444b41bba656e
08:46:33 <C-Keen> ah my bad
09:26:40 <crc> C-Keen: putn displays a number
09:26:59 <crc> I'll modify the introduction to make this clear
09:27:28 <crc> scj: not as part of the standard releases
09:28:30 <crc> I wasn't able to find a decent way to implement it in any of the implementations other than C, and it wasn't reliable on anything except for OS X and Linux
09:36:25 <retro_commits> vm: html5: fix output area wrapping when tablet mode is used on a low-res screen : http://rx-core.org/rx.fossil/info/1dc02fec31b3f0f86480fcd7058b245f8e728ee1
09:43:21 <retro_commits> vm: retro w/sockets support [experimental] and sockets' vocabulary : http://rx-core.org/rx.fossil/info/dae9b4914855fa13bcf4e5e8dc6cac55f9ed27b5
09:44:05 <crc> scj: that commit is the socket support added to the latest implementation in C, and a corresponding vocabulary to use with it
09:55:19 <C-Keen> crc: yeah after reading the whole manual it became clear to me
09:55:40 <C-Keen> crc: I am intrigued to implement the vm in scheme...
09:56:11 <crc> I'd love to see a scheme implementation
09:59:18 <C-Keen> the vm looks simple enough :)
11:37:06 <retro_commits> docs: in the introductory text, clarify the usage of 'putn' (thanks to C-Keen for bringing this up) : http://rx-core.org/rx.fossil/info/ed035491d3f6075982c650dfa3f5d6ac06094fda
11:45:06 <C-Keen> crc: OPCODE 6: should read "remove top item of address stack and push it to the data stack" correct?
11:45:58 <crc> yes
11:46:21 <C-Keen> I guessed so ;)
11:46:59 <retro_commits> docs: in opcode listing, fix a typo for opcode 6 (POP); thanks again C-Keen : http://rx-core.org/rx.fossil/info/34180f479801f27904b3e0f2a558b0e3a3076b2c
11:47:50 <C-Keen> also if you speak of branching I guess this assumes that I should push the current ip to the address stack?
11:49:42 <C-Keen> so the RETURN does the inverse of branching
11:50:08 <crc> only implicit cals push the ip to the address stack
11:50:22 <C-Keen> what about LOOP?
11:50:31 <crc> *calls, not cals
11:52:25 <crc> no, LOOP is a jump style instruction, not a call to a subroutine
11:53:01 <C-Keen> so the "branch" in the explanation is a simple jump?
11:53:07 <crc> yes
11:53:11 <C-Keen> I see
11:53:14 <C-Keen> thanks!
11:54:02 --- quit: scj (Ping timeout: 258 seconds)
11:54:32 --- join: scj (scj@shells.mycrosoft.us) joined #retro
11:55:00 <retro_commits> docs: in opcode list, note that LOOP performs a jump, not a call to a subroutine : http://rx-core.org/rx.fossil/info/ac8fb08b3c4fc2cee9bda0f4f4321ed6b00cd8d8
11:58:24 <C-Keen> sorry for disturbing your routine ;)
11:59:05 <crc> not a problem
11:59:53 <crc> when I get busy, I take longer to respond, I try to keep an eye on the channel and answer questions when I can :)
12:00:39 <C-Keen> fair enough ;)
12:15:27 <C-Keen> another question: What happens if the arguments for SHR and SHL are negative? do the inverse command?
12:25:25 <crc> good question. This is currently undefined behavior
12:26:08 <C-Keen> good, this means I can do whatever I see fit ;)
12:31:23 <crc> yes
12:33:38 <retro_commits> docs: in opcode list, note that shifts by negative values are implementation defined. : http://rx-core.org/rx.fossil/info/3160689902d86ad859e8a1889e41d9b1bf7bcc42
14:33:21 --- quit: Kumul (Quit: gone)
23:59:59 --- log: ended retro/11.11.09