00:00:00 --- log: started forth/05.04.23 00:05:09 --- quit: anto9us ("Chatzilla 0.9.68a [Firefox rv:1.7.6/20050317]") 00:38:42 --- quit: swalters (Read error: 104 (Connection reset by peer)) 01:09:27 --- quit: Sonarman ("leaving") 02:28:26 --- join: brainZzZ (apodidae@c-67-165-125-224.hsd1.wa.comcast.net) joined #forth 02:32:55 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 02:33:00 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 06:48:26 --- join: tathi (~josh@pcp01375108pcs.milfrd01.pa.comcast.net) joined #forth 07:06:46 --- quit: Hyrax ("Chatzilla 0.9.68a [Firefox 1.0.3/20050418]") 08:21:22 http://retroforth.org/handbook/home.html 08:21:22 http://retroforth.org/tutorial/home.html 08:21:22 My work in progress on the documentation :) 08:25:56 nice 08:28:40 in design philosophy (handbook) you have "you'll may yourself: Why..." 08:30:31 still a work in progress... 08:32:43 yeah. 08:37:36 --- join: Topaz (~top@sown-87.ecs.soton.ac.uk) joined #forth 08:53:38 --- join: snoopy_1711 (snoopy_161@p54A7F786.dip.t-dialin.net) joined #forth 09:00:34 --- quit: saon (Read error: 110 (Connection timed out)) 09:16:23 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 09:16:28 --- nick: snoopy_1711 -> Snoopy42 10:06:48 Should I merge the tutorial into the handbook? 10:07:45 * tathi thinks it would be nice to have a link from the handbook, at least... 10:08:17 so yeah, maybe 10:09:22 --- join: T0paz (~top@sown-85.ecs.soton.ac.uk) joined #forth 10:11:47 --- quit: Topaz (Read error: 113 (No route to host)) 11:14:52 --- join: }Topaz{ (~top@sown-87.ecs.soton.ac.uk) joined #forth 11:15:22 --- quit: T0paz (Read error: 113 (No route to host)) 11:38:18 --- part: brainZzZ left #forth 11:58:03 --- join: saon (1000@c-66-177-224-130.hsd1.fl.comcast.net) joined #forth 12:10:48 --- nick: }Topaz{ -> T0paz 12:10:50 --- nick: T0paz -> Topaz 12:37:57 --- join: zoly (~l@p549DC4F2.dip.t-dialin.net) joined #forth 12:38:07 --- quit: tathi ("leaving") 12:38:41 g'day 12:53:10 --- quit: Topaz (Read error: 113 (No route to host)) 13:00:42 --- join: sproingie (~chuck@64-121-15-14.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 13:11:18 --- part: zoly left #forth 13:32:26 --- join: Sonarman (~cleetus@adsl-64-160-166-196.dsl.snfc21.pacbell.net) joined #forth 14:17:20 --- quit: swalters ("User disconnected") 14:32:33 --- quit: sproingie ("Konversation terminated!") 14:39:20 --- join: Herkamire (~jason@c-24-218-95-147.hsd1.ma.comcast.net) joined #forth 14:39:20 --- mode: ChanServ set +o Herkamire 14:45:36 --- join: slava (~slava@CPE00096ba44261-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 14:59:51 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 15:32:33 http://forthworks.com/blog/?p=48 15:32:57 i think tutorial should come first 15:33:03 why? 15:33:10 good question :) 15:33:42 The handbook is mainly intended for those already familiar with Forth, as is the current tutorial 15:34:15 I plan to write a better tutorial for those who don't know Forth 15:34:26 cool 15:34:45 i'll point people learning factor to your tutorial too :) for grasping stack manipulation and such 15:34:51 cool 15:35:08 right now i'm working on a new reference manual, with two parts -- language/library and development tools. the second part is done 15:36:15 I'm still in the early stages of actually getting the RetroForth Handbook to a useful state 15:36:32 i've redone my docs sevearl times now 15:36:41 its hard to find the right balance between introductory material and a reference guide 15:36:59 * crc remembers when RetroForth's documentation consisted of a (short) README file 15:42:27 --- quit: qFox ("this quit is sponsored by somebody!") 16:34:19 * crc finally merged the 386 assembler from Albert van der Horst into the library 16:35:36 that assembler is terrible :/ 16:36:15 I know 16:36:30 it does work though 16:37:01 so you'll rewrite your words to use this assembler? 16:37:04 mine still hasn't progressed beyond a couple of instructions (push, pop, mov, drop) 16:37:04 no 16:37:05 instaed of hard-coded constnats 16:37:14 why not? 16:37:18 I'll still use hard coded constants in the core 16:37:37 I don't want to have to depend on an assembler to bootstrap the core startup code 16:37:48 why not? 16:37:57 the assembler is not too big is it? 16:38:11 6k of source, in block format 16:39:36 3638 bytes as a traditional file 16:40:08 RetroForth's startup code is 2736 bytes 16:40:21 And the assembler depends on some of the words in it 16:41:11 i don't think you'd lose any users by increasing the startup code to 9kb :) 16:41:30 --- join: TheBlueWizard (TheBlueWiz@ts001d0635.wdc-dc.xod.concentric.net) joined #forth 16:41:35 I'd still have to use hardcoded constants in places though 16:41:42 hmm 16:42:36 Either that or shift more of the words to precompiled part, which I refuse to do 16:42:55 metacompiling is an option :) 16:43:07 then you'd only need to load the assembler while metacompiling 16:45:01 I will metacompile at some point in the future 16:45:39 i don't think i ever will 16:47:31 heh 16:47:48 Factor is significantly more complex than RF though 16:48:18 also its not x86-only :) 16:48:52 true 16:49:18 * crc is planning to start work on PPC and ARM versions of RF later this year 16:49:29 --- quit: nasdaq ("Client exiting") 16:50:16 --- join: Frek (2432-ident@h89n2fls31o815.telia.com) joined #forth 16:58:30 --- quit: saon ("Leaving") 16:59:41 NOOO 16:59:42 lol 17:00:10 arke: ? 17:00:20 16:58 -!- saon [1000@c-66-177-224-130.hsd1.fl.comcast.net] has quit ["Leaving"] 17:01:42 --- join: saon (1000@c-66-177-224-130.hsd1.fl.comcast.net) joined #forth 17:10:54 crc, you'd have to teach me ARM assembly :) 17:15:52 ok :) 17:16:23 it can't be much worse than x86 assembler... ;) 17:17:01 ppc is really simple 17:17:23 my x86 assembler is 273 lines, ppc is 74 17:17:39 both are far from complete, but they both support about the same percentage of cpu features 17:19:23 :) fun 17:19:44 http://paste.lisp.org/display/7676 would load into any forth, you'd just have to rename a handful of words. it doesn't use any oop features at all 17:20:42 slava: lately, I've been working on herkforth to make it so it stores each definition seperately 17:20:54 what does that mean? 17:21:17 no more blocks? 17:21:20 so instead of having my source in blocks 17:21:31 so how does the editor look now? 17:21:34 each word has a chunk of data with the source tokens for it's definition in it 17:21:55 would be cool if there was still some kind of logical groupings, for editing several related words at once 17:22:05 I don't think I'm going to change the way the editor looks 17:22:34 hey, i should try herkforth in my imac! 17:22:41 I'll still have blocks, as a user concept 17:22:42 will it run over ssh or does it need direct virtual console access? 17:22:48 I'm basically just changing the implementation 17:23:02 slava: is "shift" a left or right shift? 17:23:08 crc, right 17:23:10 sorry, left 17:23:20 works over ssh 17:23:21 crc, 10 2 shift . => 20 17:23:27 i mean 40 :) 17:23:34 runs on linux, (any architecture supported by qemu) 17:23:34 Herkamire, ok, i'll try it right now 17:23:42 Herkamire, i don't have a keyboard/mouse on the mac, taht's why i asked 17:23:46 its a 233mhz g3 17:23:58 doesn't run on osx 17:24:03 this is linux/ppc 17:24:06 cool 17:24:11 no way i'd run os x on a g3 :) 17:24:21 or java, for that matter 17:24:27 :) 17:24:36 slava: ok 17:25:11 slava: you could try my newly written herkforth crash course :) 17:25:12 http://herkamire.com/jason/herkforth_crash_cours 17:25:14 Herkamire, it works 17:25:18 http://herkamire.com/jason/herkforth_crash_course 17:25:24 is there an 'e' there? 17:25:28 good :) 17:25:29 http://herkamire.com/jason/herkforth_crash_course exists 17:25:40 yeah, I didn't paste too well there 17:26:13 how do i remove a word from the editor? 17:26:26 \ 17:26:35 this is a very interesting UI 17:26:38 slava: what is compile-cell ? 17:26:47 mmm... that would be a good thing to have in the crash course :) 17:26:55 crc, i guess its like 4, or something 17:27:02 crc, adds a 4 byte literal to the compiled code area 17:27:11 crc, ppc instructions are always 32 bytes so you won't need 3, 2, 1, 17:27:14 err, 32 bits 17:27:16 i can't type today 17:27:18 I decided I wanted a different key to delete one letter on the input line, than the key that deletes words from the source 17:28:43 Herkamire, this is really cool 17:28:48 :) thanks 17:28:54 slava: one more question 17:28:58 What is w>h/h ? 17:29:33 crc, word to half/half 17:29:35 : w>h/h dup -16 shift HEX: ffff bitand >r HEX: ffff bitand r> ; 17:29:44 you give it a 32-bit integer, it pushes the high/low 16 bits 17:32:28 oh, as I was saying, I'll still display the source in blocks. 17:32:45 (blocks as a user interface, not an implementation) 17:32:56 http://paste.lisp.org/display/7676#1 17:33:12 the implementation of the source blocks will be a small data object for each block listing which definitions appear there. 17:33:50 Herkamire, ah, that's cool -- 'logical' blocks 17:35:03 crc, nice 17:35:50 I agree that there needs to be groupings of definitions 17:35:59 and they should probably be grouped manually by the user 17:36:31 I haven't implemented the new blocks yet 17:36:33 you could have a key that takes the word under the cursor, and makes a new block listing all the words that use that word 17:36:46 i use this feature in factor all the time (except it just prints a list, no blocks :) 17:36:50 --- part: TheBlueWizard left #forth 17:37:00 but I've got code to go through the dictionary, and create a data object with it's definition 17:37:44 in the future, herkforth will be able to have a listing of words/definitions like that 17:37:52 that can be the results of any sort of query 17:37:58 neat 17:38:05 currently the editor can only display source blocks 17:38:10 but in the future, it will be more flexible 17:38:26 eg it could display all words that start with ed- 17:38:30 yup 17:39:06 or words that use the current word is a good one 17:39:20 the first one is useful too, i have an 'apropos' word for that 17:39:44 currently (repository only I think) there's a key to see the next usage of a word, so you can browse through the places it's used. that's very handy 17:40:56 not sure how I'll implement this. I'll probably have a memory space that is a sort of block that the editor overwrites when you do such searches 17:41:17 this merging of the editor and interpreter is neat 17:41:37 :) 17:41:48 oh, I thought you were doing that too 17:42:03 you were using jedit... that's right 17:42:19 its not as integrated 17:42:21 you had some way of executing stuff without leaving the editor iirc 17:42:33 yes, i can select a range of text and execute it 17:42:46 it just sends it over a socket 17:43:17 I find the tight integration extremely productive 17:43:22 no doubt 17:44:09 the editor will be expanded later to be able to edit different things 17:44:12 like text 17:44:17 tables 17:44:23 and eventually images 17:45:47 will there be comments? :) 17:45:54 heh :) 17:46:08 yeah, something like that 17:47:06 have you seen squeak before? where you're heading is a forth equivalent (but much lighter). that's very cool 17:47:15 I want to have accessible documentation about each word 17:47:22 and have it hooked into the wiki 17:47:35 yeah, I've played with squeak 17:47:37 very cool 17:47:48 but horrid UI and the graphics were a bit slow on my machine 17:48:21 I was very very impressed by how easy it was to find the source code for stuff and fix it! 17:48:26 the concepts behind the UI are good but the usability is poor, and the graphics are just done by writing to a framebuffer 17:48:32 but quite dismayed that nobody had done so... 17:48:54 what sort of concepts? 17:49:09 well, you can edit any object through the UI 17:49:23 you build your program's UI while it runs, so to speak 17:49:24 it may very well have not been their fault it was slow, graphic things tend to be slow on my X 17:49:28 because there's no edit time/run time distinction 17:49:39 right. that is very cool 17:49:42 well, it doesn't even use X, other than mapping a shared memory buffer. you can run squeak without X, in fact 17:49:49 I mean like the scrollbars and clicking on everything is horrid 17:49:53 yeah 17:50:04 on my machine it feels slower than swing 17:50:44 yeah, I know, but theres something slowing it down. probably some kind of protected memory checking or something 17:51:16 I have some weird (possibly hardware) problem that makes it so I can't switch away from the X VT and back without losing my display 17:51:21 squeak is also a bytecode interpreter :) 17:51:31 yeah 17:52:08 it's a shame 17:52:14 there's a lot of really cool stuff out there 17:52:24 some awesome concepts, some great implementations 17:52:30 but few combine both :) 17:52:40 but so much of it just has such horrible interfaces that I don't want to use them 17:53:11 all this focus on the concepts and stuff, and they forget to pay attention to the users/programmers 17:53:12 its hard for us programmers to make good UIs though... because we understand the workings of our programs, so some things seem intuitive that don't to a casual user 17:53:28 eh 17:53:38 that too 17:53:41 i mean, it takes user feedback to make a good UI 17:53:51 but I mean like sit and program for an hour, and pay attention to what you waste time doing 17:53:56 then change it so you don't have to do that anymore 17:54:02 yes, that too 17:54:13 I don't think most of these systems are very productive for the people who made them either 17:54:46 true 17:54:53 I tried some obscure language last year (dylan or something) and it seemed really neet, but the hello world program took some increadibly long time to compile (like 20-30 secconds) 17:55:05 I was totally miffed 17:55:09 dylan has exceptionally verbose syntax 17:55:20 how could people sit and try to write software with those sorts of compile times? 17:55:23 yes, i hate long turn-around times too. i prefer not having to restart anything at all, and just reload code 17:55:28 debugging must be absolute hell 17:55:38 debugging is already the biggest time waster of all 17:55:50 we need to develop systems for making the debugging go quicker 17:55:51 java has this problem, except its not as bad as 30 seconds on my machine, but still a waste of time to recompile/restart 17:56:19 being able to edit code in the running image is a good first step 17:56:42 herkforth can recompile all it's code instantly 17:56:44 woohoo -- i just got my C library interface working on PowerPC 17:56:52 nice :) 17:57:01 well, i haven't fully tested it yet... just some simple functions 17:57:04 i should try SDL or something. 17:58:12 heh -- i wonder how slow my mandelbrot program will run on this mac :) 17:58:33 can you mmap /dev/fb ? 17:58:56 i don't see why not 17:59:02 but i already have code for the sdl binding, that's all 18:00:28 oh, I was just thinking that maybe you could run the herkforth mandelbrot code, but I just remembered you're running it over ssh 18:00:57 yah, i gave the imac's kb and mouse to my sister (she got herself a powerbook and likes using a real kb and mouse when she's not on the road.) 18:03:36 yep 18:08:54 lemme know if you have any ideas for herkforth 18:09:13 and I want to know what's confusing and annoying etc 18:09:43 --- join: CXDoctor (~rex@pcp0010699353pcs.manass01.va.comcast.net) joined #forth 18:10:38 Herkamire, nothing confused me yet :) 18:11:15 ! :) 18:12:02 hey Herkamire 18:12:27 I just got the herkforth src dl'd on this mac- it's macosx. how do I build? 18:12:53 a) start linux 18:12:55 b) make 18:12:56 :) 18:13:13 or should I peek at the doc/ dir for this info 18:13:47 CXDoctor: it doesn't run on osx 18:13:54 aw rats 18:13:55 I started porting it, but never finished 18:14:32 I probably should finish the port 18:14:35 I probably would of played around with it for like 10 minutes and left it alone anyway 18:14:48 it's been sitting, half done for many months 18:15:33 yah man, once you've covered x86 and ppc, you're set for making the majority happy.. even the weird guys with other architectures would understand why you dont have ports like sparc ,etc 18:15:38 I kept thinking that I should just get the native version done, so anybody with a mac could just boot it regardless of OS 18:15:57 or that, ya 18:16:04 cx, herkforth is ppc only 18:16:17 works on qemu :) 18:16:26 is it fast? 18:16:27 herkforth runs on spark just as well as x86... through qemu 18:16:49 everything but the mandelbrot is plenty fast under the emulator 18:17:09 complete recompile and save is still instant 18:17:44 you need linux though 18:18:08 well, might work on osx under qemu 18:18:26 I wonder if there is a liveCD linux for ppc 18:18:35 CXDoctor: sure is 18:18:40 CXDoctor: I've used several 18:18:50 or at least two 18:18:53 cool, what's the closest to knoppix? 18:18:57 or what's your fav 18:18:58 lol 18:18:59 that's generally how you install linux 18:19:13 ranlib: .libs/libSDL.a: No space left on device 18:19:15 NOOO 18:19:26 slava: is it really full? 18:19:45 oh, I don't know a good bootable linux that's good for just using. I always just use them to get linux installed 18:20:00 yah I meant those demo cd's 18:24:42 yeah, I've run into them before, but I don't remember the name of any 18:27:44 CXDoctor: how long you going to be around? 18:30:01 heh. iono im just taking looks into 'more native langs' than java for my language. for now, im decided on C, but if a forth impresses me enough... 18:30:26 so Im lead to ask crc about retroForth too, lol 18:31:17 cool 18:31:21 what sort of language you working on? 18:31:35 I'm going to see if I can get herkforth to run on osx now 18:31:41 cool 18:32:27 my lang isnt closely related to anything that exists already. some ideas from lisp, a coincidence of similarity with newLisp in the OO, and syntax like nothing I've seen before 18:33:11 prefix syntax, really- here http://contex.sf.net 18:33:56 * Herkamire looks briefly 18:34:47 I gotta make one of my last java releases tonight. it's alot better in cvs right now 18:35:01 CXDoctor: what are you lead to ask me about? 18:35:27 could I get retro to run on macosx? 18:35:34 which download, if so? 18:35:46 retro is written in x86 assembly 18:35:52 fun 18:36:07 CXDoctor, gforth is written in C, if you want a C forth 18:36:18 ehhee 18:36:21 CXDoctor: you can run the native version in Qemu or Bochs 18:36:22 gforth for a c forth 18:36:32 gforth is quite fast 18:36:48 Or run the L4 version under Qemu 18:36:51 yeah, very fast for a C forth 18:36:58 and for an interpreted language in general 18:37:14 nah, I wouldnt want to build a language ontop of a language ontop of assembly ontop of an emulator ontop of macosX 18:37:21 just doesnt sound cool 18:37:44 ? 18:38:23 nvm that. Ill try gforth 18:44:01 ga! this mach-o file format is freakin rediculous 18:44:16 Herkamire, haha indeed 18:44:23 seems to me the smallest possible header size (no linking, just one load) is 340 bytes 18:54:25 heh, I'm not putting that whole ugly thing in with , 18:54:39 $feedface , $12 , ... 18:54:47 lol 18:57:09 is zoly around any more? 18:57:15 is he the guy that did the JSForth? 18:57:36 yes 18:57:42 zoly was here earlier today 18:57:55 I was just at google, doing the google.calc(expr) thing :) and thought it would be really cool for zoly to have his jsforth as part of the front end search system of google. 18:58:08 maybe he should contact google. :) wouldn't that be slick as sh*t! 18:58:17 heh 18:58:43 at the search engine, you could just typing jsforth and you'd get the runtime up and going :) 18:58:52 * crc should see about writing the "retro" vocabulary for JS-Forth at some point 19:02:31 crc should indeed get up off his forth cheek and do it. 19:02:32 :) 19:04:28 Al2O3: work on RetroForth 8 is higher priority for me ;) 19:17:56 crc, anyone doing it for PPC, or am I still the one man in the shoot/slot for it. 19:18:07 I heard someone else was gonna get started, but never did. 19:18:26 * Al2O3 is currently getting JSforth working in Ruby. 19:18:37 Darn thing almost translates directly. 19:18:49 Al2O3: I hope to get some stuff on RetroForth/PPC working this summer 19:19:20 * crc ported Slava's PPC assembler to RF today 19:19:20 it would be slick as snot if you got a bridge to cocoa working too :) 19:19:27 neat 19:19:41 slick as snot, lol 19:19:48 is slava's ppc assembly in/post fix, or prefix? 19:19:56 prefix 19:20:08 postfix 19:20:32 it just takes the register numbers and operands from the stack 19:33:51 hmmm... one part of this mach-o-header business I'm not sure about 19:34:01 --- quit: Fractal (Read error: 110 (Connection timed out)) 19:34:13 --- join: sk1p_ (alex@p548D659E.dip.t-dialin.net) joined #forth 19:38:57 do osx binaries really have to be a multiple of 4KB? 19:45:46 --- quit: sk1p (Read error: 110 (Connection timed out)) 19:48:49 Herkamire: that would be screwed up... 19:49:48 I think that's the case 19:50:02 well, I doubt herkforth will be running on osx by the end of the night 19:50:49 maybe 19:50:53 I'm getting a little boored though 19:53:19 btw, to all the forthers here, get out and build a kite and relax for a day :) I built my first kite in about 25 years today. SPent about 3 bucks in materials, made a box kite, it flies, and the kids are stoked to fly it tomorrow (tonight I test flew it around the neighborhood behind my bicycle at dusk). 19:53:36 Its related to forth, only in that the box kite has 4 sides :) 19:53:37 Herkamire, windows is the same 19:54:05 I love vim: :s/\(..\)/\~\1/g 19:55:17 puts a hexdump (with just the straight hex chars) into my ~ encoding. here's my elf header: 19:55:21 ~7f~45~4c~46~01~02~01~00~00~00~00~00~00~00~00~00~00~02~00~14~00~00~00~01~10~05~1d~50~00~00~00~34~00~00~00~00~00~00~00~00~00~34~00~20~00~01~00~28~00~00~00~00~00~00~00~01~00~00~00~00~10~00~00~00~10~00~00~00~00~05~1d~94~00~10~00~00~00~00~00~07~00~01~00~00 19:56:28 .....lol.... 20:00:45 --- quit: danniken () 20:24:02 --- join: docl (~main@dpcbw101009.direcpc.com) joined #forth 21:08:48 --- quit: swalters ("User disconnected") 21:13:30 --- quit: CXDoctor (Remote closed the connection) 21:13:55 --- join: Fractal (jah@selling.kernels.to.linus.torvalds.at.hcsw.org) joined #forth 21:14:39 --- join: CXDoctor (~rex@pcp0010699353pcs.manass01.va.comcast.net) joined #forth 21:17:55 Al2O3: hehe, i like your nick. i've been using electrolysis to dissolve metals; yesterday i made Al(OH)3 21:18:34 i posted a weblog entry about the PowerPC port of Factor's C library interface: http://www.jroller.com/page/slava/ 21:29:24 anybody want to give my a shell account on a Mac OS X box so I can debug herkforth for osx? 21:32:38 goodnight 21:32:53 'night crc 21:39:31 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 22:46:31 --- quit: CXDoctor ("but I'm still not a quitter") 23:01:54 --- quit: docl (Remote closed the connection) 23:31:25 herkforth is mostly working on Mac OS X :) 23:31:36 --- quit: Herkamire ("off to bed") 23:59:59 --- log: ended forth/05.04.23