00:00:00 --- log: started retro/12.10.11
00:24:58 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
00:32:16 --- quit: ncv (Ping timeout: 240 seconds)
00:54:38 --- quit: jyfl987 (Ping timeout: 246 seconds)
01:00:08 --- join: jyfl987 (~jyf@unaffiliated/yunfan) joined #retro
03:43:23 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
04:26:16 --- quit: ncv (Ping timeout: 260 seconds)
05:29:13 <crc> tangentstorm: assuming that the docstrings all start with a stack comment, I can export them into a markdown document and render to HTML instead of using the manually updated table
05:29:23 <crc> http://rx-core.org/list.html
05:29:43 <crc> I'll find this very useful :)
06:03:47 <tangentstorm> nice! :)
07:08:14 <tangentstorm> woohoo! got permission to release the pascal-in-forth this guy wrote back in 1983 :)
07:12:13 <crc> cool
08:11:31 --- join: Mat2 (53f1ea04@gateway/web/freenode/ip.83.241.234.4) joined #retro
08:11:36 <Mat2> hello
08:20:05 --- quit: Mat2 (Quit: Page closed)
08:20:28 <tangentstorm> hey Mat2 :)
08:32:29 <tangentstorm> oh :)
09:06:28 --- join: ncv (~quassel@89.123.22.68) joined #retro
09:06:28 --- quit: ncv (Changing host)
09:06:28 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
12:10:26 <crc> rev 391 adds "make docstrings" to export Markdown copies of the documentation
13:42:52 <tangentstorm> :) yay for automation!
14:07:20 <tangentstorm> crc: so... i'm kind of stirring things up in #lpmc today ( the learn programming mentoring community from reddit i mentioned a while back )
14:09:13 <tangentstorm> can i offer up retro as a project ? 
14:20:30 --- quit: jyfl987 (Ping timeout: 255 seconds)
14:20:51 --- join: jyfl987 (~jyf@unaffiliated/yunfan) joined #retro
14:41:57 <crc> tangentstorm: yes
14:50:51 <tangentstorm> sweet :) 
15:41:04 --- quit: ncv (Ping timeout: 260 seconds)
16:19:40 --- join: Mat2 (5b4085c5@gateway/web/freenode/ip.91.64.133.197) joined #retro
16:19:43 <Mat2> hello
16:25:31 <tangentstorm> heya Mat2 
16:25:50 <Mat2> hi tangentstorm !
16:27:10 <Mat2> i'm lost in effective hashing this week ;)
16:28:27 <tangentstorm> oh ?
16:29:35 <Mat2> <- implementing a dictionary as hash table
16:30:37 <tangentstorm> did you ever get your code up online?
16:31:12 <Mat2> yes, tomorrow night
16:31:29 <tangentstorm> i've been playing around with your "programmable instruction set" concept for retro / ngaro
16:32:03 <Mat2> what are your experiences so far ?
16:34:03 --- join: kumul (~kumul@cvx-ppp-66-50-130-239.coqui.net) joined #retro
16:34:29 <tangentstorm> i didn't try to get down to 4 bits / opcode ... i just left a block of 256 cells to allow for a programmable bytecode
16:35:46 <tangentstorm> hi kumul.
16:36:06 <Mat2> hello kumul
16:36:24 <Mat2> tangentstorm: have you take a look at my github repro ?
16:36:27 <kumul> erm, hello? xD
16:36:29 <Mat2> https://github.com/Mat2/extended-ngaro
16:37:30 <tangentstorm> Mat2: nope. not until just now. :)
16:37:51 <tangentstorm> kumul: just saying hi.. i always see you coming in here, but don't know who you are :)
16:38:46 <tangentstorm> Mat2: "retrospect" haha... great name
16:40:00 <Mat2> *lol* if I remember correctly, this was the name choosen from crc for his older debugger
16:40:15 <Mat2> version
16:42:57 <tangentstorm> Mat2: so you can compile ngaro instructions to native code with this?
16:43:04 <Mat2> yes
16:43:27 <Mat2> and the generated native code exetnd the instruction set
16:43:35 <Mat2> sorry I mean extend
16:45:15 <Mat2> this combined with experiments for an effective interpretative instruction-set and code format leads to my current vm design
16:47:05 <tangentstorm> Mat2: very very cool
16:47:36 <Mat2> tomorrow night you will find my current sources here:
16:47:40 <Mat2> https://www.assembla.com/spaces/navm/wiki/b54XdmfKWr34DXeJe5afGb?version=15
16:48:21 <tangentstorm> I will look for it. :)
16:50:34 <kumul> tangentstorm: not much to say really, joining because i like listening to conversations i dont understand ( like the current one :)
16:50:57 <tangentstorm> kumul: hahaha... it's okay, i don't know what i'm talking about either half the time ;)
16:51:44 <Mat2> kumul: read this - http://www.retroforth.com/docs/An_Introduction_to_Retro.html
16:52:02 <tangentstorm> Mat2: does this navm still support the virtual devices like ngaro?
16:53:22 <tangentstorm> "7. Effective and fast threading mechanism"
16:53:25 <tangentstorm> :)
16:53:25 <Mat2> no, it uses a system interface based upon exception handling (like SWI on ARM compatible cpu's)
16:54:43 <Mat2> kumul: you will also like to read this - http://home.iae.nl/users/mhx/sf.html
16:56:35 <tangentstorm> I'm not familiar with ARM... What I'm thinking about is ngaro as a competitor to LLVM 
16:59:13 <Mat2> oh, and I am thinking of using LLVM and openCL as immediate representation for the compiler
17:00:28 <Mat2> my first version (the github one) was based upon gnu's lightning
17:01:49 <Mat2> the problem I see is: Both LLVM and openCL are huge and very academic envirioments and I hate to use bloated code
17:02:41 <tangentstorm> i guess i misunderstood what i was looking at. i thought you were just hand generating assembly.
17:03:33 <Mat2> (beside that, LLVM generate at current impressive bad code for x86)
17:04:01 <Mat2> ^yes, that is the case
17:04:38 <Mat2> but I had experimented with other code generators before
17:04:42 <tangentstorm> Mat2: I know oberon has a cross-platform compiler infrastructure... I  haven't really looked at it, but it should be very small.
17:04:50 <tangentstorm> it's called FOX i think
17:06:23 <tangentstorm> http://www.ethoberon.ethz.ch/native/compiler/
17:06:35 <tangentstorm> i don't think that's the cross-platform one though... they have several
17:07:00 <Mat2> I know this one but don't have any experiences with ist other than its predecessor OBERON 5 compiler
17:07:25 <Mat2> OBERON is a nice operating system by the way
17:08:18 <tangentstorm> yeah :) 
17:08:34 <kumul> Mat2: can retro behave silently? without all those ok's ?
17:09:17 <Mat2> kumul: yes, you need to write your source code in a file and start retro this way:
17:09:31 <Mat2> retro --with <file name>
17:11:28 <kumul> using 11.5 and it shows ok on each line
17:11:33 <tangentstorm> kumul: the "ok" reply is in kernel.rx ... you can change it there and type "make image" and it'll rebuild
17:12:26 <Mat2> or use a pipe
17:12:29 <tangentstorm> you can also patch it dynamically  using  "is" ... but i've not done that yet, so i'm not sure how to tell you how to do it
17:12:43 <tangentstorm> Mat2: it still says ok all the time :) after every word
17:13:41 <Mat2> ??? don't have these problem here
17:14:34 <tangentstorm> kumul: ./retro --with examples/editor.rx    then type edit   to see a ui that escapes the listener    (  type z to go back )
17:14:35 <kumul> yep, its great for debugging but not so good if you just want it to behave like most languages
17:15:13 <tangentstorm> Mat2: i hadn't thought of it as a problem... it's just what it does.  what vm do you use?
17:15:25 <Mat2> 11.4
17:15:35 <tangentstorm> retro.c ?
17:17:49 <tangentstorm> kumul: it's not really going to work like most languages... :) but you can just type "clear" after you load an *.rx file
17:18:10 <crc> kumul:   [ ] is ok
17:18:53 <tangentstorm> crc: :) oh. that's pretty darn easy i guess :)
17:20:22 <tangentstorm> " devector ok "  to restore... awesome!
17:21:43 <Mat2> I will get some sleep, ciao
17:21:54 --- quit: Mat2 (Quit: Page closed)
17:46:14 <kumul> aha! was doing it wrong! a {  : main clear "hello world" puts bye ; main  } did what i wanted, thanks tangentstorm and crc
17:51:04 <tangentstorm> :)
19:46:39 <docl> howdy all
19:46:55 <docl> kumul: congrats on getting it working :)
20:39:15 <docl> really liking the new help modules in retro
21:00:19 <docl> feels like it's missing a libraries function
21:01:26 <docl> chwords is quite nice though
21:34:44 --- quit: kumul (Quit: zZZzzZzzz)
22:38:43 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
23:59:59 --- log: ended retro/12.10.11