00:00:00 --- log: started retro/06.07.10 03:08:55 anybody an idea why an invalid machine command happens? 03:32:46 in your code? 03:33:03 " foo " 2dup + 'a swap c! 03:33:21 'a will be stored right *after* the string 03:33:38 ehm, yes 03:33:40 in a definition, this will overwrite the machine code that follows the string 03:33:51 oh.. 03:34:00 " foo " 2dup + 1- 'a swap c! 03:34:26 two spaces at the end of the string, and a 1- after adding will keep it in the safe region 03:34:40 ok.. 03:36:04 I thougth, that s" foo" saves the string in the word and when the word gets executed, it puts the string into pad 03:36:28 no, putting the string in pad only happens in the interpreter 03:37:53 " foo " pad swap copy 2dup + ..... 03:37:56 this would work 03:38:37 ok, sry, my mistake 03:39:08 not a problem 04:11:08 and did you try one of those directfb things? 04:17:37 --- quit: virl (Remote closed the connection) 04:36:07 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro 05:56:16 --- join: Ray_work (n=Raystm2@199.227.227.26) joined #retro 05:59:47 --- join: nighty (n=nighty@66-163-28-100.ip.tor.radiant.net) joined #retro 06:41:52 * docl wants to try directfb, but hasn't figured out how yet 07:28:01 Hi docl :) 07:28:12 * Ray_work had lots of fun playing with the retro 07:28:30 good, knew ya would :) 07:28:42 isn't it beautiful? 07:28:49 absolutely. 07:29:02 I was stunned when I read the repos 07:29:27 using rx-core, and making a port looks like it's pretty simple thing. 07:29:55 I think it's a new beginning of forth 07:30:09 yeah, it really sets the bar 07:30:39 i've been playing with editing a 'save-game.txt' file by hacking the 'block' directly, which is what i'll need to do to make the chess persistance work. 07:30:49 BUT 07:31:06 i think I will be using the editor commands as part of the code, afterall. 07:31:39 this willbe different then the gforth/win32forth version, can't be helped. 07:32:23 it shouldn't be too hard to port the commands to another forth, seems like 07:34:25 how does gforth load/save files? 07:42:36 It's similar to how crc does it. of course the names of the words have been changed to protect the innocent, 07:42:53 ahh, I see :) 07:43:09 something allong the lines of... 07:43:19 0 value fd-file 07:43:24 then you 07:43:53 make several words to open close and read and right that throw to that file descripter value. 07:44:06 right = write even 07:44:40 so, more complex in other words 07:44:44 yes 07:44:48 I think it is. 07:45:13 but then crc has already wrapped the c functions that do all that. 07:45:29 gforth version could be simplified by encapsulating those words, probably 07:46:11 so your new code would still be portable 07:46:50 there is a thought. 07:47:14 . o O ( : <-- lnparse 2drop ; might be a nice commenting word (on another topic) ) 07:48:17 : end foo bar save ; <-- does stuff then saves 07:49:19 looks nice in irc, but would it seem tacky in code? 07:50:55 now, in html there's a similar piece of code used for commenting 07:50:58 by the way, what should a portable forth include? 07:51:29 there's a big question 07:52:41 it should encapsulate platform-specific code in small modules that can be changed around, for one thing 07:53:33 I'm still planning my xell thing 07:55:45 stuff to handle things like endian-ness, cr/lf, keycodes, etc. needs to be seperated from the more functional code 07:58:09 I guess with byte-streaming, the only thing you need watch for with endian-ness is in IP addresses, right? 08:00:41 well, I depend not on ip 08:01:22 xell is a bit more abstract 08:02:03 kind of like rx? 08:02:14 yeah, like rx. 08:05:30 are you more interested in writing your implementation in c or fasm? 08:06:24 in c, fasm I don't have really a glue about it. 08:06:56 you could create a functional equivilent of Rx in c (reading is probably easier than writing), then make whatever mods you feel would make it fit the xell concept. 08:09:43 or, just use it for ideas 08:12:37 my concept of forth is there's these areas of memory (heap, pad, stack, input buffer, editor blocks, dictionary) that are all simply being manipulated by the words 08:16:21 my one, so the xell concept is lower ;-) 08:19:44 so a portable forth is just a set of memory blocks that are manipulated, and some good words to manipulate them with 08:20:34 yep.. 08:20:44 and then there is ans forth... 08:21:50 a set of particular words to manipulate memory with particular names 08:22:13 there's no rule that says you need to call swap, dup, and drop by those names either 08:22:55 ...e.g. K or bf 08:23:19 forth is just a way of organizing things so they are easier to do 08:24:18 now, for portability you do need some kind of code that reads these memory blocks and communicates with devices and other programs properly with them 08:24:43 trouble is this code isn't itself portable, so it needs rewritten for each platform 08:35:03 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #retro 10:26:03 * docl loves using screen 10:27:16 I have it set to switch screens when I press C-Z and C-X 10:28:03 * virl loves using ion 10:28:42 I used that for a while, but stopped for some reason 10:32:14 hmm? 10:39:49 * docl just reinstalled ion 10:43:50 I was having trouble with some of the keys, but they work great this time :) 11:50:53 one trouble I have is xterm keeps coming up with a white background, and I can't figure out where to reconfigure it 12:03:01 well, there are some ionscripts written in lua 12:05:33 well, copy all the files /etc/X11/ion to .ion 12:05:59 and then modify your home copy of the scripts, so that it draws a black background(-bg black) 12:27:24 which script do I put this in? 12:31:23 puh, ehm.. 12:31:30 don't know, grep 12:32:14 * docl is doing that 12:51:57 figured it out. had to put some stuff in .Xresources and run xrdb from .xinitrc 13:08:32 aha, ok, I solved it different 13:12:59 one slightly annoying thing about x11, there's a zillion ways to do anything 13:13:55 --- quit: nighty ("Disappears in a puff of smoke") 13:55:27 we love x11, don't we? 13:55:30 :-D 14:33:33 oh yeah :P 14:39:13 --- join: Shain (i=steve@c-67-161-56-76.hsd1.ca.comcast.net) joined #retro 14:39:47 I think I prefer icewm to the other wm's I've tried. 15:02:01 good evening 15:02:43 hi crc 15:03:27 --- quit: Ray_work (Read error: 104 (Connection reset by peer)) 15:55:35 --- join: nighty (n=nighty@CPE00508be190fc-CM0012253ec1bc.cpe.net.cable.rogers.com) joined #retro 16:16:03 crc, what do you think about reva? 16:16:34 it looks like that it's more for windows 16:37:15 it says it's for linux and windows both... 16:45:43 retro compiled with the help module crashes when run 16:49:14 two problems: 1) compat was not at the right spot in the list of modules, 2) it didn't have :: defined. 17:20:16 --- quit: neceve (Remote closed the connection) 17:20:33 --- join: nighty_ (n=nighty@CPE00508be190fc-CM0012253ec1bc.cpe.net.cable.rogers.com) joined #retro 17:21:00 --- quit: nighty (Read error: 104 (Connection reset by peer)) 18:08:14 reva is a decent forth, but larger and more complex than retro 18:09:13 it is more focused on speed on modern processors 18:09:18 and has turnkey support 18:10:30 docl: the help module is going to be rebuilt from scratch 18:22:02 --- quit: nighty_ (Read error: 110 (Connection timed out)) 18:22:30 --- join: nighty (n=nighty@CPE00508be190fc-CM0012253ec1bc.cpe.net.cable.rogers.com) joined #retro 18:53:58 Playtime. 19:25:43 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-135-254.pools.arcor-ip.net) joined #retro 19:33:10 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 19:33:20 --- nick: snoopy_1711 -> Snoopy42 19:57:57 --- quit: nighty ("Disappears in a puff of smoke") 20:21:50 * Raystm2 will need clear to clear 9 more lines 20:41:25 Raystm2: download the 902-beta.tar.gz again and use the new binary 20:41:36 it should clear everything 20:57:19 :) thank you 20:57:34 * Raystm2 playing with a board but no pieces as yet. 21:05:47 new clear works great. thank you. ;) 22:53:49 --- quit: Snoopy42 (clarke.freenode.net irc.freenode.net) 22:55:07 --- join: Snoopy42 (i=snoopy_1@dslb-084-058-135-254.pools.arcor-ip.net) joined #retro 23:59:59 --- log: ended retro/06.07.10