00:00:00 --- log: started forth/04.10.21 00:36:19 --- quit: wandelf ("Download Gaim: http://gaim.sourceforge.net/") 00:43:57 --- join: mur_ (~mur@kyberias.uiah.fi) joined #forth 00:52:41 --- quit: mur (Read error: 110 (Connection timed out)) 01:40:44 --- quit: SDO (Read error: 60 (Operation timed out)) 02:14:53 --- join: mur (~mur@uiah.fi) joined #forth 02:24:52 --- quit: warpzero ("Tried to warn you about Chino and Daddy Gee, but I can't seem to get to you through the U.S. Mail.") 02:25:05 --- quit: mur_ (Read error: 110 (Connection timed out)) 02:44:11 --- quit: Zymurgy ("Leaving") 03:26:15 --- join: crc (crc@29-pool1.ras11.nynyc-t.alerondial.net) joined #forth 03:33:25 --- join: mur_ (~mur@uiah.fi) joined #forth 03:43:18 --- quit: mur (Read error: 110 (Connection timed out)) 04:14:58 --- quit: crc (Read error: 232 (Connection reset by peer)) 04:15:06 --- join: crc (crc@40-pool1.ras11.nynyc-t.alerondial.net) joined #forth 04:43:57 --- quit: Raystm2 ("User pushed the X - because it's Xtra, baby") 04:44:51 --- join: mur (~mur@uiah.fi) joined #forth 04:52:00 --- quit: crc (Read error: 104 (Connection reset by peer)) 04:52:37 --- join: crc (crc@117-pool1.ras11.nynyc-t.alerondial.net) joined #forth 04:55:24 --- quit: mur_ (Read error: 110 (Connection timed out)) 05:12:17 --- join: wincent (~wincent@void-109.pmnet.uni-oldenburg.de) joined #forth 05:28:11 --- join: mur_ (~mur@uiah.fi) joined #forth 05:39:12 --- quit: mur (Read error: 110 (Connection timed out)) 05:51:08 --- quit: crc (Read error: 104 (Connection reset by peer)) 05:51:16 --- join: crc (crc@233-pool1.ras11.nynyc-t.alerondial.net) joined #forth 06:30:02 --- join: I440r (mark4@216-110-82-59.gen.twtelecom.net) joined #forth 06:30:15 Hi 06:30:54 Hello Robert 06:33:22 rather quiet this morning... 06:33:24 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 06:33:24 --- mode: ChanServ set +o Herkamire 06:33:40 crc: Yeah, except it's not morning. 06:33:43 Hi Herkamire 06:34:03 Robert: it's morning here :-) 06:35:04 But I don't live in Oz. 06:35:24 Oh, well, I went up late enough for this to count as morning. 06:35:28 :-) 06:35:49 * crc has been updating the RetroForth documentation and working on the 7.5 release 06:37:37 * Robert checks the home page 06:37:44 hi Robert :) 06:38:00 crc: cool :) how's the native version coming? 06:38:08 Not too bad 06:38:36 The supported drivers are pretty solid now, and I'll have a port of VIBE running on it very soon 06:38:46 20kB of code and 6 years of development? 06:38:58 How many bits is that per day? ;) 06:39:39 I'm not sure :-) 06:42:05 It's about half the size that 4.0 was, despite having much more functionality :-) 06:44:58 After I release 7.5, I'll be focusing on getting VGA support in place 06:45:18 * crc is also doing some work on getting RetroForth to run on the L4 microkernel 06:45:25 Cool! 06:45:35 I should check it out...after this nap. 07:02:34 --- join: mur (~mur@uiah.fi) joined #forth 07:03:35 If the interpreter encounters an undefined word, should it stop interpreting or ignore it? (either way, it will be reported) 07:05:18 (The compiler just reports the error and continues compiling, so I'm wondering if I should modify the interpreter to do the same) 07:13:32 --- quit: mur_ (Read error: 110 (Connection timed out)) 07:14:01 --- quit: wincent (Remote closed the connection) 07:14:21 --- join: wincent (~wincent@void-109.pmnet.uni-oldenburg.de) joined #forth 07:18:23 oh, that would be great to have VIBE :) 07:18:52 crc: it should definitely stop 07:19:01 crc: especially when compiling files/blocks 07:20:23 even on the cmdline it can be important, eg if you have a typo in a variable name or something 07:20:43 "my-ver @" should print word-not-found, not crash 07:26:16 good point 07:30:32 * crc will leave the interpreter alone then 07:32:21 --- join: mur_ (~mur@uiah.fi) joined #forth 07:34:32 --- quit: mur (Read error: 60 (Operation timed out)) 07:36:45 --- join: hefner (~hefner1@linux3.gl.umbc.edu) joined #forth 07:41:22 huh? it should _not_ continue 07:41:52 The current behavor of the interpreter is to stop 07:42:19 The compiler continues compiling right now 07:44:47 it should stope compiling 07:44:51 slava: why? 07:45:07 "fail early, fail often" ;) 07:45:16 crc, i wrote a simple drawing application in factor 07:45:29 slava: cool 07:45:30 i have to allow resizing and deleting existing shapes, and different colors now 07:45:40 crc: oh :) I didn't realise the interpreter and compiler behave differently 07:45:43 slava: it reports the errors, why stop the compile 07:45:50 crc, then i guess its ok 07:45:53 crc: why continue? the code isn't going to work anyway 07:45:57 crc, still what if you have this 07:46:05 : foo bafdas ( mistake ) ! ; 07:46:07 123 foo 07:46:09 crc: also, it could crash the same way my example above 07:46:09 in a block 07:46:24 it might burn badly 07:46:31 anyway, i have a midterm exam now, bye all 07:51:15 * crc searches for a clean way to stop compiling... 07:53:55 I can compile a 'ret' into the the definition, and continue compiling the rest of the word 07:54:06 Or I can just compile the rest of the word 07:54:13 or forget the word? 07:54:33 oxygene: that would be too complex 08:00:39 * crc hates hacking the compiler code 08:01:02 If I just break out of the compiler loop, the rest of the line gets interpreted 08:01:27 * crc might just compile a 'ret' and the rest of the definition 08:08:26 --- join: crc_ (crc@95-pool1.ras11.nynyc-t.alerondial.net) joined #forth 08:11:23 --- quit: crc (Read error: 104 (Connection reset by peer)) 08:12:18 --- nick: crc_ -> crc 08:16:04 --- quit: I440r (Excess Flood) 08:16:15 --- join: I440r (mark4@216-110-82-59.gen.twtelecom.net) joined #forth 08:51:21 --- quit: mur_ (Remote closed the connection) 08:52:22 --- join: mur (~mur@uiah.fi) joined #forth 08:54:22 --- quit: crc (Read error: 60 (Operation timed out)) 08:56:29 --- quit: Baughn (Read error: 54 (Connection reset by peer)) 08:56:31 --- join: Baughn (~svein@cloud.brage.info) joined #forth 08:59:46 --- join: ows (~ows@a81-84-114-35.netcabo.pt) joined #forth 09:40:35 --- join: fridge (~fridge@dsl-220-253-73-135.NSW.netspace.net.au) joined #forth 09:48:28 --- join: warpzero (~warpzero@dsl.103.mt.onewest.net) joined #forth 10:06:53 --- join: mur_ (~mur@mgw2.uiah.fi) joined #forth 10:09:15 --- join: Yoroa (~n7r7l3@cw07.F2.srv.t-online.de) joined #forth 10:09:29 --- quit: Yoroa (Excess Flood) 10:09:51 --- quit: mur (Read error: 60 (Operation timed out)) 11:07:21 --- join: Teratogen (leontopod@slashsnot.org) joined #forth 11:29:27 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 11:38:13 --- join: fridge_ (~fridge@dsl-203-33-163-230.NSW.netspace.net.au) joined #forth 11:47:08 --- join: warp0x00 (~warpzero@mi189.dn179.umontana.edu) joined #forth 11:54:13 --- quit: fridge (Nick collision from services.) 11:54:15 --- nick: fridge_ -> fridge 12:15:53 --- quit: hefner (Read error: 104 (Connection reset by peer)) 12:18:08 --- part: swsch__ left #forth 12:51:11 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 12:54:28 --- quit: ayrnieu (Read error: 232 (Connection reset by peer)) 13:19:29 --- join: slava_ (~slava@CPE00096ba44261-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 13:21:26 --- nick: mur_ -> mur 13:28:23 --- quit: slava (Read error: 113 (No route to host)) 13:31:07 anybody here familiar with colorforth? my code ain't working 13:31:08 TYPE unpack 0 if space drop drop ; next emit type ; 13:31:08 HW 70 256 * dup type 2 + type ; 13:31:09 HI show black screen hw keyboard ; 13:31:41 basically 70 is the block that has the "hello world" 13:32:12 hmm maybe i forgot to fetch? 13:32:58 nah no fetch needed 13:33:23 Oooh, read-only code! 13:33:47 actually fetch needed.. and i did forget to do FFFFFFF0 AND on it 13:34:04 Robert: are you kidding? 13:34:32 paste any non-forth code and i assure you i won't understand it one bit.. even C :P 13:38:13 its ok, you can speak, i'm not looking for a flamewar 13:38:43 has anyone here read "the humane interface"? i just read it again and i want to discuss it.. 13:42:48 futhing.. cant read the code, i dont see the colors 13:44:50 Stepan: the stuff in bold is red.. the rest is green 13:45:30 colorforth's IF is non destructive right? 13:52:37 hmm i found some coloforth code that does hello world in the same way that i was trying to do it lol 13:53:15 so...did you figure out why yours didn't work? 13:53:22 (I have read THI, btw) 13:53:45 tathi: yeah its because i wasn't fetching from the address and masking it 13:54:46 gotcha 13:54:52 tathi: well i've been thinking of implementing some of ideas of THI in colorforth.. but i can't figure out how to have the whole os as one large flat document AND have zoomable interface 13:54:58 you just didn't say whether it actually worked after that, so... 13:55:10 well i'm at the library 13:55:21 so no real way of testing my code :) 13:55:34 hmm...I have some reservations about the zooming thing. 13:56:20 I guess my main issue is that I think I want things to be more like links, rather than "zooming in" to a sub-object. 13:56:48 I mean, what if you have something "contained" in several places? 13:58:10 well thats ok i think.. multiple paths to get to that something based on the context that you are working in 13:58:23 yeah, I suppose. 13:58:47 I also don't understand how it would work in some cases -- like in herkforth's interface 13:58:57 you have a command to go to the definition of the word 13:59:14 what's it going to do, zoom in until the blank space is big enough, and then display the definition in it? 13:59:20 just sounds ugly. 14:00:11 ok, sorry to go off on a tangent 14:00:35 why can't you have one flat document and zooming? 14:01:20 probably can 14:01:35 but in zooming, the "flat document" isn't portrayed sequentially 14:01:40 you've got all these boxes all over the place 14:01:43 and within each other 14:02:14 err...sequentially? 14:02:19 so it seems confusing to LEAP sequentially within the "flat document" and also zoom around 14:02:28 oh. 14:02:34 s/sequentially/linearly 14:03:05 yeah, that's my biggest objection to Jef. He has some really neat ideas, but he leaves a lot out when it comes to putting them all together. 14:03:24 hmm...I've always sort of thought that you need keys to navigate within a history of where you've been. 14:03:57 well in his book is like chapter 2 to 4 is the scientific part 14:04:05 and some of chap 5 14:04:09 and the rest of the book is all his ideas 14:04:13 yeah. 14:04:14 his 1980's ideas heh 14:04:19 but his ideas seem kind of disconnected 14:04:23 yup 14:04:33 I'm not sure if he hasn't put them together yet 14:04:36 he doesn't really explain the rationale or keep it rigorous etc 14:04:41 or if he just thinks it's obvious how they fit together :) 14:05:29 heh 14:05:33 yeah i understand that too 14:05:52 i know that if i tried to explain some of my ideas i'd be like Jef 14:05:56 He seems to have text-editing pretty much figured out. 14:06:06 half of it would be grounded in science, the other half would just seem "obvious" to me :P 14:06:11 But I don't see how his principles for THE would extend to, say, image editing. 14:06:33 yup :) 14:06:43 that's what makes it so hard to write good documentation 14:07:09 the stuff that people need explained is often the stuff that's obvious to you. 14:07:24 yeah i definitely want to extend his stuff for image editing, etc 14:07:29 but i think i have some ideas there 14:07:32 cool 14:07:55 ok, want my thoughts on LEAP/zooming? 14:08:12 if I can present them in a coherent fashion? :P 14:08:15 yes please :) 14:08:49 if you're zooming/panning, you're going to a spatial location 14:08:58 you know where the thing is, because you put it there. 14:09:20 if you're LEAPing, you're looking for specific information, you don't necessarily care where (spatially) it is. 14:09:45 yeah 14:09:52 if you LEAP somewhere, occasionally you may want to zoom out and find out where you've got to (spatially), so you can come back later. 14:10:08 but I *think* that usually you'll just be looking for specific information 14:10:22 and once you find it, you'll want to be able to just pop back to whatever you're working on. 14:10:32 the concepts seem somewhat orthogonal to me. 14:10:42 different means of navigating for different purposes. 14:10:47 --- quit: wincent (Remote closed the connection) 14:11:10 I *do* think you need a LAST command (or something) to go back where you were before you LEAPt 14:11:47 hmm i guess he didn't explicitly mention that 14:11:55 Personally, I want to try having a full history tree, with the ability to choose between branches when you're going forward. 14:11:55 well he sort of mentions osmething like that 14:12:08 I don't remember him connecting LEAP and the zooming interface at all. 14:12:08 where you leap to a word, then backtrack and leap to a different word 14:12:15 yeah he didn't heh 14:12:19 oh, a back button 14:12:25 right. Now I'm wit' ya. 14:13:55 hmm...where did I put that book... 14:14:01 :) 14:14:19 well i was thinking that the flat document would be completely open 14:14:24 i.e. no hidden info 14:14:27 ok 14:14:46 so i guess the spatial information would be stored in the first block of each document 14:15:07 where document is the "unit" of information.. the "boxes" that you see while zooming around 14:15:34 right 14:15:52 I'm not so interested in having herkforth in a zooming thing 14:16:03 i was thinkign of extending colorforth piecemiel until i had something like THE 14:16:05 more like jumping around 14:16:09 so i would keep the blocks 14:16:28 I may try a zooming interface for navigating source, but more as a curiosity experiment. 14:16:58 Herkamire: so your mind rebels against the usefulness of a zooming interface? ;) 14:17:10 futhin: no, I just don't think it's the most useful way to do herkforth source 14:17:22 well, not source. 14:17:24 futhin: I would very much like to try it for organizing my files 14:17:30 yeah, data. 14:17:39 *gasp* the f word :P 14:17:41 I hesitated before saying "files" 14:17:44 :) 14:18:11 is herkforth ppc specific? 14:18:16 herkforth's go-to-def is kinda like zooming in, but going back isn't always teh same as zooming out 14:18:19 heh 14:18:20 futhin: yes 14:18:44 for example you can find-next and back and out would be totally different things 14:19:11 basically herkforth already addresses the main benifits I imagine a zooming interface would give 14:19:34 and is better in some ways, eg you can fit a lot more source on the screen 14:19:47 and getting where you want is often instant 14:20:05 yah, that's my other objection to zooming 14:20:12 I don't want to have to wait for it to go somewhere 14:20:33 tathi: yeah, I'm worried about that too 14:20:44 Like even the zoomy rectangles on old MacOS were really annoying sometimes. :) 14:20:48 I think a zooming interface would be wonderful for data that I don't use much 14:21:04 but anything that I do a lot I should be able to do quick by typing something shortish 14:21:23 tathi: yep :) 14:22:21 futhin: I'm (hopefully soon) going to release a pre-built version of herkforth all set up to run under qemu on other architectures 14:23:11 I just have to do a couple hacks to get around the two ioctls I use that don't work under qemu 14:24:07 huh? zooming wouldn't fit less source on the screen 14:25:44 sure it would 14:25:49 some is going to be really big 14:25:56 and some will be too small to read 14:26:01 --- join: hefner (~hefner1@linux3.gl.umbc.edu) joined #forth 14:26:09 so the amount of legible text will be reduced 14:32:26 um.. 14:32:48 thats only when you're seeing more than one box 14:33:01 if you've zoomed into a box of source 14:33:04 then its going to fill up the entire screen 14:33:20 and then if you zoom in to the definition of one of the words in that screen? 14:33:22 and its going to fit as much source as a non-zooming interface 14:33:44 yeah i guess you could do that too 14:34:04 no, I mean, then what would it look like? 14:34:09 that's what he's talking about 14:34:10 here's an example: http://herkamire.com/downloads/src-zoom.png 14:34:27 that's how the interface on herkforth works, except it's more like a link. 14:34:44 you're looking at some source, you have a key to go to the definition of the word under the cursor. 14:34:56 right 14:35:23 it shows the definition of what's under the cursor near the bottom of the editor. a key takes you to the definition 14:35:32 well when you zoom into a link, like the definition of one of the words in the screen, basically it just pops you into the new window 14:35:53 its not going to show text within your current window like a magnifying glass 14:35:57 its going to act like a link 14:35:58 futhin: how is that better than just hitting the link? 14:36:12 hitting the link with what? 14:36:13 futhin: then it's not zooming. then zooming is just stupid eye candy 14:36:31 no the zooming exists for the content that you arrange spatially and within each other 14:36:34 for the actual links 14:36:38 like when you zoom into a webpage 14:36:50 in a zooming interface, as described in THI, there is no morphing or anything things don't dissapear and be replaced by smaller things 14:36:55 then it just pops you into the page that was linked to 14:36:58 it works just like a magnifying glass, you just zoom in 14:37:44 wrong, he describes where you zoom into the patient's heart rate info etc, and if you zoomed into a technical word, it pops you into a medical reference book 14:38:01 i.e. it acts as a link at the deeper levels of the zoom 14:38:01 oh 14:38:07 ok 14:38:34 actually i think he describes that on the webpage rather than the book? i'm not sure 14:38:40 or mabye he doesn't describe that at all 14:38:46 and that was my original interpretation :P 14:39:01 I don't remember it, but it sounds plausable 14:40:04 anyway, sounds terribly silly for the herkforth source editor 14:40:43 so that picture is your source eidtor? looks really cool! :) 14:41:01 futhin: no, I made that in sodipody (vector editor) 14:41:25 this is herkforth: http://herkamire.com/jason/herkforth_screenshot 14:43:52 so typing below the line of the asterix is how you input code? and it gets stored to the editor? 14:43:59 tathi: In my herkforth for qemu package, I'm going to ship the set-term and restore-term you wrote a long time ago for fpos :) 14:44:09 er.. 14:44:14 tcsetattr doesn't work in qemu 14:45:14 there's an input line at the bottom, much like irssi 14:45:21 except space and return both clear it 14:45:46 the white box is my terminal's cursor, where text is input 14:49:23 futhin: actually in THI he makes it sound like it always zooms in. 14:49:30 that was my main objection. 14:49:38 if it just pops you there, then that's cool. 14:50:45 --- join: Sonarman (~matt@adsl-67-113-235-157.dsl.snfc21.pacbell.net) joined #forth 14:51:09 Herkamire: I thought my set-term and restore-term used the ioctl that tcsetattr calls? 14:54:11 hrm...I'm just finding set-term and restore-term written in C, that use tcsetattr 14:55:32 you have something else? 14:57:56 I mean the little C programs 14:58:07 I'll have them compiled to the native architecture. 14:58:27 ah. 14:58:28 gotcha. 14:58:29 and have a script that calls them (and qemu-ppc herkforth inbetween) 14:58:31 clever 15:02:16 ok, I'm off to dinner and juggling 15:02:27 have fun 15:03:13 futhin: speaking of Jef, do you know how he feels about other people using his ideas? 15:03:25 I mean, he has a patent on the LEAP keys thing. 15:03:31 So I'm curious. 15:04:54 bastard 15:05:05 ok, really gone 15:27:00 --- quit: warp0x00 (Read error: 54 (Connection reset by peer)) 15:32:03 --- join: warp0x00 (~warpzero@mi189.dn179.umontana.edu) joined #forth 15:36:12 --- quit: qFox ("this quit is sponsored by somebody!") 15:41:10 Aha. 15:41:46 "LEAP and its related methods are patented, and no commercial or distribution license is afforded by this description or the open-source implementation being made public." 15:42:07 "Personal or developmental use is encouraged. LEAP is a trademark." 15:42:15 :( 15:42:35 What is it about? 15:43:08 --- quit: warp0x00 (Read error: 232 (Connection reset by peer)) 15:44:39 --- join: warp0x00 (~warpzero@mi189.dn179.umontana.edu) joined #forth 15:44:56 In Jef Raskin's book "The Humane Interface" he describes a method of searching, which he calls LEAP. 15:45:06 see also http://humane.sourceforge.net/ 15:45:09 Searching what? 15:45:09 OK 15:45:12 text 15:45:19 he's a user-interface guy 15:45:24 Ah, OK. 15:45:36 largely responsible for the design of the Classic Macintosh 15:57:02 futhin: ah, looks like if you LEAP, then want to go back, you use UNDO. 16:00:02 back :) 16:00:09 interesting tho.. 16:00:20 guess we don't need a leap-undo command then :P 16:02:46 --- join: ez4 (~ez4@pcp01518726pcs.reding01.pa.comcast.net) joined #forth 16:03:30 * futhin had to go pick up a tire 16:06:44 I'm not sure I like that, but whatever. 16:06:56 hmm 16:07:00 (UNDOing LEAPS, not you going to pick up a tire :P) 16:07:10 :) 16:07:13 oh wait. 16:07:16 undo is a key. 16:07:26 yeah 16:07:29 I keep forgetting that. 16:16:09 well, enough of this high-level nonsense -- I'm going back to designing my assembler :) 16:16:12 --- quit: tathi ("leaving") 16:16:40 --- quit: warp0x00 ("leaving") 16:17:02 heh 16:17:08 dang 16:17:21 somebody tell me about tathi's assembler 16:17:41 i want colorforth to metacompile i think 16:37:13 --- join: unfies (~unfy@sillyness.org) joined #forth 16:45:41 hi unfies :) 16:46:31 and hi ez4 16:46:32 Silly forther. 16:46:41 Robert: whom? 16:46:56 --- quit: hefner (Remote closed the connection) 16:47:17 it's interesting how few new ppl this channel gets 16:47:25 all the new ppl never talk or something 16:47:30 --- join: hefner (~hefner@pool-151-196-120-221.balt.east.verizon.net) joined #forth 16:47:30 and then leave eventually 16:47:34 after they realize we're all mad? 16:48:05 futhin: unfies. 16:49:32 i'm just here to say hi to i440r, that's all :) 16:49:38 --- part: unfies left #forth 16:49:45 heh 16:49:50 too much text! 16:49:56 * futhin blames robert 17:01:16 --- nick: slava_ -> slava 17:01:24 Hi Sonarman 17:01:25 er 17:01:27 Hi slava 17:01:28 hi 17:10:07 hi anyway, Robert 17:10:14 :) 17:10:31 I have enough love for the both of you. 17:12:14 yay! 17:12:53 Robert my love! 17:13:59 *kusje* 17:17:10 this ANS version of P[ was a lot more difficult to write than i expected 17:17:14 ans hate 17:17:25 P[ ? 17:17:26 arke hate 17:17:33 Haha. 17:17:51 postpone foo postpone bar 2 postpone literal postpone + ----> P[ foo bar 2 + ]P 17:18:12 Ah, I see. 17:18:32 because i have to build a big-ass string to be EVALUATEd later on 17:18:50 with gforth i can just compile postpones 17:19:06 with factor, 17:19:18 : quux [ parsed ] each ; 17:19:28 : bah [ foo bar 2 + ] quux ; parsing 17:20:08 slava, you're so cruel 17:21:18 but on the plus side, this also resulted in a cool bunch of words for building strings 17:21:55 --- quit: cmeme (zelazny.freenode.net irc.freenode.net) 17:22:20 --- join: cmeme (~cmeme@216.184.11.30.unused.swcp.com) joined #forth 17:22:25 --- join: I440r_ (mark4@216-110-82-59.gen.twtelecom.net) joined #forth 17:22:44 with the gforth-only version of P[ : 17:23:01 : foo P[ dup 2dup 1 + ]P ; immediate ok 17:23:01 see foo 17:23:01 : foo 17:23:01 268600172 compile, 268600204 compile, 1 compile-literal 268599820 compile, ; immediate ok 17:23:05 with the ANS version : 17:23:25 : foo P[ dup 2dup 1 + ]P ; immediate ok 17:23:25 see foo 17:23:25 : foo 17:23:25 s\" [ get-order 805518376 805518336 805518336 3 set-order ] dup 2dup 1 + [ set-order ] " evaluate ; immediate ok 17:24:05 i have to preserve the search-order of when FOO was written 17:28:25 * futhin has no real idea what postpone, defer, etc are for, and whether or not they are necessary etc 17:28:34 but i tend to say "what would chuck moore do?" 17:28:36 :P 17:28:44 he would not have P[ 17:28:47 and neither would I. 17:29:03 sonarman is trying to make some string to be evaluated later on 17:29:12 i suspect p[ isn't necessary for that 17:30:20 Sonarman: pls tell me that p[ IS necessary :) 17:32:36 i'm not a pro forther or anything 17:32:46 i may be talking out of my ass 17:34:34 --- quit: cmeme (Broken pipe) 17:35:24 making a string to be evaluated later on is necessary for P[ (in a forth that only provides ANS words) 17:35:37 --- quit: ows (Excess Flood) 17:35:45 otherwise you could just compile compile 17:35:54 --- join: cmeme (~cmeme@216.184.11.30.unused.swcp.com) joined #forth 17:35:59 which is teh hella easiar 17:36:08 --- join: ows (~ows@a81-84-114-35.netcabo.pt) joined #forth 17:37:30 i moved the search-order preservation out of the evaluated string 17:38:20 which makes things slightly chuckier 17:38:26 but still not nice 17:38:39 hahaha... chuckier is the best adjective ever 17:39:45 * Robert chuckles. 17:40:43 Sonarman: i thought you were making P[ for the purpose of making a string to be evaluated later on? 17:41:05 or are you making P[ for the heck of it and you require the ability to be able to evaluate a string later on? 17:41:05 gah... circles 17:41:19 P[ creates a string to be evaluated later on 17:41:26 it's just a convenience word 17:41:45 so that you don't have to type POSTPONE oever and over again 17:42:04 Color! Color! 17:42:22 POSTPONE mode! 17:42:39 2test 17:42:42 4whee 17:42:52 6omg liek mirc is teh best 17:43:28 (sorry about all the crazyspeak; this room reeks of cleaning chemicals) 17:44:31 5,1test 17:44:43 5,1test 17:44:46 oooh 17:46:09 11223344556677889900 17:46:13 112233445566778899 17:46:55 1one2two3three4four5five6six7seven8eight9nine0zero 17:48:02 0Hello World 17:48:21 Heh. 17:48:22 5w 9@ fffffff0 and 17:48:26 I440r_: he's distracted! now's your chance to take back the channel@ 17:48:38 5ww 9unpack if emit ww; then space drop drop ; 17:49:06 5hw9 60 block dup w 1+ w ; 17:49:11 5hello 17:49:28 world 9show black screen text hw keyboard ; 8hello world 17:49:32 damn! 17:49:38 5world 9show black screen text hw keyboard ; 8hello world 17:49:56 yay for spam in the guise of code ;) 17:52:01 does it look alright to you guys? 17:52:16 we shouldn't be afraid to use color for colorforth code :P 17:54:29 the yellow-on-white is unreadable, but that's my problem, not yours 17:54:45 ah heh 17:54:57 i sort of figured your client would turn it to the inverse 17:55:58 since i'm only doing ctrl-C 8 for yellow (for example).. because i'm not doing 8,1 or 8,0 i'm not assigning a background color.. so the irc client should adapt to make it visible 17:56:02 i dunno 17:56:07 :P 17:58:34 8,0test 17:58:36 8,1test 17:58:41 oooh fun 18:05:28 :) 18:14:39 --- join: warp0b00 (~warpzero@mi173.dn179.umontana.edu) joined #forth 18:31:52 --- quit: ows ("Client Exiting") 18:41:50 --- join: Zymurgy (zymurgy@delgw.delfax.net) joined #forth 18:52:53 --- join: SDO (~SDO@67-23-111-213.clspco.adelphia.net) joined #forth 19:43:30 i hereby call my colorforth + THE os implementation Flite 19:43:36 let the logs record that 19:43:37 mwahaha! 20:01:22 --- join: chriswalton (~newbie@wbar8.lax1-4-11-100-111.dsl-verizon.net) joined #forth 20:01:46 --- part: chriswalton left #forth 20:20:12 --- quit: Sonarman (Read error: 54 (Connection reset by peer)) 20:24:36 --- join: Sonarman (~matt@adsl-64-160-165-18.dsl.snfc21.pacbell.net) joined #forth 20:43:54 --- quit: wossname () 20:44:46 --- join: wossname (~wossname@rn-v1w5a06.uwaterloo.ca) joined #forth 20:53:47 --- quit: SDO (Read error: 110 (Connection timed out)) 21:26:19 rrrrrrr 21:26:22 anybody seen Hero? 21:43:58 --- quit: Sonarman ("leaving") 21:48:03 --- quit: wossname (Connection timed out) 21:56:36 --- join: crc (~crc@h-64-105-207-163.phlapafg.covad.net) joined #forth 22:03:38 --- quit: hefner ("zzz") 22:31:07 --- quit: Herkamire ("leaving") 23:09:20 --- join: mur_ (~mur@mgw2.uiah.fi) joined #forth 23:12:12 --- quit: mur (Read error: 60 (Operation timed out)) 23:15:50 --- quit: Baughn (Read error: 60 (Operation timed out)) 23:20:54 --- join: mur (~mur@mgw2.uiah.fi) joined #forth 23:23:41 --- join: ok (r@core-dc-1-100.dynamic-dialup.coretel.net) joined #forth 23:31:13 --- quit: mur_ (Read error: 238 (Connection timed out)) 23:47:53 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 23:59:59 --- log: ended forth/04.10.21