00:00:00 --- log: started retro/11.04.13 07:03:45 --- join: aisa (~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net) joined #retro 09:10:03 --- join: PoppaVic (~pops@unaffiliated/poppavic) joined #retro 09:10:26 crc: you up, hoss? 09:13:42 buggers. 09:13:45 --- part: PoppaVic left #retro 10:13:05 --- join: PoppaVic (~pops@unaffiliated/poppavic) joined #retro 10:13:12 howdy 10:13:22 welcome :) 10:13:58 anyway, 10.2.1 has the assembler code in image/cross.toka; the language the assembler is written in is toka, this is in the toka/ directory 10:14:07 well, I been whacking on an engine for the last year or three. I have a bit of a different twist in mind, but as usual we al seem to intersect 10:14:14 HAH! 10:14:42 crc: I knew it ;-) I remembered the nagaro/toka and whatnot discussions from prior years. 10:15:23 Your C is fairly attractive, btw. Some bit of redundancy therein, but it's clean. I like that. 10:15:29 thanks 10:16:00 I was remembering the occasional i440r visits to ##C and was scared to look, initially ;-) 10:16:40 reading the "pAvm" post at the moment. Not sure if it matters. 10:18:47 crc: so, is retro getting used much? 10:22:16 I use it daily, not sure about anyone else 10:22:41 embedded, I presume? or just standalone projects? 10:22:51 (everyone is into embedded, anymore) 10:23:23 Although the def of "embedded" seems to have gone mad. 10:23:36 standalone projects mostly. I've done a little work with building embedded devices using an ARM processor and Retro, but it's a bit resource heavy for real embedded uses 10:23:55 hm 10:24:39 I tend to think embedded as either from-C or as "ported somewhere as we used to port FIG". 10:24:58 and ficl, alas, is still flakey. 10:25:27 I've got a couple of public web apps (a blog, and an irc log viewer) written in retro (http://rx-core.org/dev/corpse and http://rx-core.org/dev/rancid) and a couple of work-related apps using it as well 10:25:37 Cool. 10:25:45 no one is embedding retro in apps yet 10:26:02 I've just recently started looking into this as a possibility 10:26:12 well, anything forthlike is still "outsider" to many. 10:27:08 (this reminds me: cfa - http://rx-core.org/retro-shared-object.tar.gz is the first test of retro as a .so; seems to work ok on my server) 10:27:13 I guess I'll have to start keeping more in-touch.. Your stuff seems pretty solid, (what I'm reading), and the uses merely continue. 10:27:43 well, yeah - it would work outta' a dynalib fine. 10:28:51 The issues with the building would be in expectations and your penchant for Standards and Portable.. There are a *lot* of people that seem adamant that "C99 is The Standard" - and it gets worse. 10:29:04 I need to build some C api to access the dictionary headers and provide more control over execution before it's practical to embed it in an app 10:29:06 with clang and gcc, I rarely have issues 10:29:17 Right. 10:29:33 the C can be compiled without problems using clang, gcc, pcc, and tcc 10:29:49 I've been trying - for a few weeks, (I've been ground looping) - to relegate headers out in an sqlite3 file. 10:32:00 I'm fairly sure my issue is a mindblock when it comes to SQL.. I'm so damned used to the simple key/value dbopen. 10:39:46 I only indirectly interface with sqlite 10:39:51 hm. well the aVm, navm, 2vm stuff seems to be vaporware. 10:40:25 crc: Yeah. I felt it would be useful to involve it. I want to get the headers entirely outside images, too. 10:40:32 at least some of the varients have code, though not public 10:40:48 dbopen was my first choice, buggerin' linux hides it behind gdbm. 10:41:35 well, when his *vm stuff shows up as a buildable tarball, I'll look. I can't embrace git/mercurial like others do. 10:42:46 and if he goes c++, I am running like hell in the other direction 10:44:47 http://rx-core.org/navm.tar.gz 10:44:57 iyah.. OK, I see the toka/build stuff ;-) Huzzah. I was going goofy! ;-) 10:45:18 ah. You been looking into it as well, I take it? 10:45:57 yes 10:46:09 General impressions? 10:46:22 not complete yet 10:46:28 well, yeah 10:47:10 the ideas and architecture look promising (though much more complex than what I use now), but until he gets around to a complete implementation, it's not usable for me 10:47:39 Yeah. I see lotsa' headers - with more license than sense. Still prowling it. 10:48:42 IIRC, most of the code is actually in the headers 10:48:59 gad 10:49:16 well, I _was_ going to aside (this C is unattractive) 10:51:18 I suspect it explains why he writes they'll be switching to c++ - I'd wager he'll go template-happy. 11:02:24 back to work for me; will return sometime tonight 11:26:30 ok 11:26:34 --- part: PoppaVic left #retro 13:50:08 --- join: erider (~chatzilla@unaffiliated/erider) joined #retro 13:50:14 hi all 14:19:57 --- join: erider_ (~chatzilla@pool-108-3-149-46.bltmmd.fios.verizon.net) joined #retro 14:20:07 --- quit: erider_ (Changing host) 14:20:07 --- join: erider_ (~chatzilla@unaffiliated/erider) joined #retro 14:21:16 --- quit: erider (Ping timeout: 246 seconds) 14:21:23 --- nick: erider_ -> erider 14:39:54 --- quit: aisa (Quit: aisa) 16:57:49 hi 17:03:48 crc: hey are you in today 17:11:22 yes 17:13:25 the experiments in building a .so of the core worked well enough; I'll do a vm specifically for this purpose (with a focus on allowing embedding/control from a host application) soon 17:14:25 --- join: roarde (~roarde@pdpc/supporter/active/roarde) joined #retro 17:14:42 hi roarde 17:14:52 evening, crc 18:15:17 --- quit: roarde (Ping timeout: 260 seconds) 18:17:31 --- join: roarde (~roarde@pdpc/supporter/active/roarde) joined #retro 18:17:51 * crc wants a non-recursive implementation of .s 18:37:06 so far the best I've come up with is: 18:37:08 : ..s 18:37:08 depth [ "<%d> " puts ] sip 0; 18:37:08 heap [ dup [ swap , ] times 18:37:08 here 1- swap [ dup @ dup putn space swap 1- ] times drop ] preserve ; 18:38:30 this pushes the max depth on the return stack to 42 cells with 60 items on the stack. The recursive .s pushes it to 192 cells. 18:40:31 or better: 18:40:33 : ..s 18:40:33 depth [ "<%d> " puts ] sip 0; 18:40:33 heap [ dup [ swap , ] times -1 allot 18:40:33 [ here @ dup putn space -1 allot ] times ] preserve ; 18:41:32 crc: what about centering all html table elements rather than left-justify? 18:42:22 I find left justified easier to read for most purposes 18:43:13 ok. stack diagrams will have to be post-processed for centering 18:44:01 I'll be working on that soon 18:44:45 cool. I can now return to my regular program. 19:24:22 roarde: the stack diagrams should be centered now 19:29:08 still wondering how to center on the "-" 19:29:26 footnote 2's table needs class corefunc, btw 19:31:36 centering the column as you've done removes much of the initial human parsing problem present before 19:32:40 ok, I fixed the table in footnote 2 19:33:02 centering on the - will be harder; I need to do more research on docutils first 19:34:32 in this case, stack must be 2nd column? 19:34:58 yes 20:13:33 crc: are you using malloc to create numbers in retro 20:14:25 malloc is used once, in the C vm, to allocate space for the image 20:14:54 it's never used by retro itself 20:15:31 ah ok 20:16:51 I working on writing a scheme interpreter 20:17:23 crc: that why I need the lesson in recursion :) 20:18:56 there are a lot of things to work on then... garbage collection :) 20:24:57 I think I am not going to worry about the gc right away 20:25:56 I just want to get the details of dealing with the semantics and syntax of an language. That is way I picked scheme 20:31:30 crc: talk to you later 20:31:35 chao all 20:31:43 --- quit: erider (Quit: ChatZilla 0.9.86.1 [Firefox 4.0/20110318052756]) 20:32:58 --- quit: roarde (Quit: Leaving) 23:59:59 --- log: ended retro/11.04.13