00:00:00 --- log: started forth/02.05.16 00:13:35 --- join: GilbertBSD (~gilbert@max2-101.dacor.net) joined #forth 00:13:46 Hey ho! 00:14:06 Hej rob_ert.se 00:14:22 how do you say 'how are you'? 00:14:37 In what language? :-) 00:14:42 duh. 00:14:46 FORTH ;) 00:14:49 ;D 00:14:58 "Hur går det?" <-- Swedish 00:15:04 "Hoe gaat het?" <-- Dutch 00:15:09 "Wie geht's" <-- German 00:15:22 I know the german and the french ones. 00:15:23 And now, teach me that expression in some weird language =) 00:15:36 'Ca va'? 00:15:54 Ohayo <-- japanese 00:15:59 Heh... "Va' sa" = "What? I didn't hear" 00:16:15 really? 00:16:16 hehehe 00:16:22 Yeah. 00:16:26 'Ca va'? <--- French 00:17:01 :-) 00:17:33 'Hur går det, gamle sjögurka?" <-- another variant in swedish 00:17:59 How are you? Is everything alright? 00:18:50 what does it mean? 00:20:35 Hmm 00:21:32 Nothing, really. 00:21:36 Made it up :-) 00:21:53 --- join: BigBoyToddy (~BigBoyTod@co-trinidad1a-22.lbrlks.adelphia.net) joined #forth 00:22:00 HI Big boy 00:22:06 gilby 00:22:12 how is the great forth documentation project going? 00:22:40 well, I have done a few more documents, and a HUGE garage sale this weekend is taking up all my time. I have 20+ systems to sell, so the forth project is on hold until monday. 00:22:48 I have some more books coming in, 4 in particular :) 00:22:55 --- quit: deltab ("Reconnecting") 00:22:59 which ones? 00:23:01 --- join: deltab_ (~deltab@216.234.235.21) joined #forth 00:23:23 With all the computers I'm selling, with a friend, and the fun we have doing this, well I hope to make a few bucks. 00:23:36 Hi BigBoyToddy :) 00:23:50 Hmm 00:23:52 where do you live again? CO? 00:24:01 * rob_ert would like to be there :( 00:24:05 * rob_ert likes computers :-) 00:24:06 The books? Lets see, FORTH for Pros, Forth Fundamentals Vol 1 (loaned), and 2 other forth documents, working on getting Kitts Peak too :) 00:24:12 rob_ert: wants to come to america? 00:24:14 GilbertBSD: yep. 00:24:18 rob_ert: hi 00:24:28 Kitts peak had a forth? 00:24:37 GilbertBSD: Yeah, I'd like to.. :-/ 00:24:39 i mean forth doc? 00:24:53 I currently have TIL, Starting forth, forth programming and more. 00:24:54 so come over rob_ert 00:25:12 --- nick: deltab_ -> deltab 00:25:26 The documents, well, polyFORTH II, USING FORTH as I stated, 83 forth standard, 79 forth standard, Kitts Peak document, Stanfords document, and more. 00:25:39 Oh, and the BYTE articles. 00:25:49 GilbertBSD: Will you pay my tickets? =) 00:25:52 I still have to scan the CM article and send it to CM :) 00:26:03 rob_ert: no your dear dad will. 00:26:13 Bah.. 00:26:16 I doubt that. 00:26:17 Just wanted to drop by and say hi, so hello to all FORTHers, here, lingering or otherwise. 00:26:20 the byte articles? I can't find those on byte.com 00:27:01 GilbertBSD: yes, the byte magazine FORTH aug 1980 issue. I have 2 copies of the mag, so cutting one up for scanning is not a HUGE problem. 00:27:30 well, I'm snoozing tired, have to go, take care all and I hope to remember to come online for CM this weekend. Sat at 2 PM pacific right? 00:28:06 I dun no 00:28:14 oh well, later then. Take care! 00:28:18 --- quit: BigBoyToddy ("See ya folks, it has been nice to chat with you all.") 00:30:58 Oh, right... Chuck's returning, isn't he? 00:32:26 --- quit: rob_ert (Remote closed the connection) 00:33:29 --- join: rob_ert (~robert@h237n2fls31o965.telia.com) joined #forth 00:52:26 --- join: davidw (~davidw@adsl-243-109.38-151.net24.it) joined #forth 00:53:08 Hi :-) 00:54:41 --- quit: GilbertBSD ("xchat exiting..") 01:24:30 --- join: Soap` (flop@203-96-99-34.dialup.xtra.co.nz) joined #forth 01:25:13 Hi Soap`. 01:31:55 --- quit: Soap` (Read error: 104 (Connection reset by peer)) 01:32:02 --- join: Soap` (flop@203-96-99-34.dialup.xtra.co.nz) joined #forth 01:32:19 doh 01:39:02 * rob_ert leaves for 1 hour of school. :-) 02:57:37 --- join: juu (ammu@baana-62-165-189-112.phnet.fi) joined #forth 03:01:30 murr 03:17:55 oh nice 03:18:00 700 ppl on one channel 03:18:00 :) 03:18:13 and someone has 83000 kicks / kickbans 03:19:01 I thought it might be cool to let people know (somehow: topic, bot, chanserv) about the event on the 18th, and interested parties to prepare "what is future of forth" opinions for C. Moore 03:19:01 Hmm 03:19:01 * rob_ert will think about that. 03:19:28 (this was several days ago... probably too late to do anything about it now?) 03:19:59 or, still thinking? 03:21:23 if you were to check the log of the last CM appearance, you will find that's -exactly- what he asked for 03:24:07 what date was the last CM appearance? 03:24:57 two weeks ago from this coming saturday, when he has said he will return 03:25:37 ugh, i'm going out of town this weekend 03:28:52 what time did he show up? 03:29:01 then, he asked for opinions on the future of forth... perhaps there were enuf people already there to form a working group to give opinion on that subject; I had thought a few days ago "it would be nice to give others (i.e., people who come here over the intervening period) an opportunity to answer the same question... 03:29:17 but when I presented the idea... 03:29:22 Hmm 03:29:25 * rob_ert will think about that. 03:29:38 hehe 03:30:01 I guess we can all breathe a sigh of "oh well" :) 03:30:11 oh dear 03:30:27 lets start massive invite / msgspam campaign ;) 03:31:04 if you do that lilo might notice you 03:32:22 but like I said, oh well... it was just a (community-building) idea... 03:32:55 it was only joke 03:33:03 it'd be just stupid to do that in any case 03:33:10 true 03:46:55 --- join: goshawk` (goshawk@panix1.panix.com) joined #forth 03:52:33 juu: ;) 03:52:42 juu: I can't set the topic here anyway 03:52:44 er 03:52:47 jim* 03:52:58 ahh :) 03:53:16 And btw, I only said I might prepare some answer to Chuck's q. 03:53:33 oic 03:55:06 rob_ert you called little one:) 03:55:25 Nah, I called the wrong troll :D 03:55:31 Sorry to bother you 03:56:35 rob_ert it's payback time 03:57:38 :-? 03:59:53 * juu gives rob_ert flowers 04:01:07 * rob_ert says "no" when juu asks him to marry him. 04:04:50 but i didn't asked anything 04:05:19 Oh... 04:05:25 * rob_ert hears voices in his head. 04:06:31 rob_ert you need advice. see a doctor 04:06:44 doctor a day keeps apples away :) 04:07:06 * rob_ert sees a flying apple. 04:07:13 * rob_ert eats doctor juu- 04:07:18 hey hey! no dissing apples! I ran forth on an apple... 04:07:43 was it drive-thru or drive-in? 04:07:44 :) 04:07:46 xD 04:07:59 Hmm... is there any forth for CP/M-86? 04:08:07 there was, yes 04:08:22 it was on one of those big floppies 04:08:33 err, cpm/80 04:08:46 still, probably is for 86 too 04:09:34 Hmm 04:09:49 Only non-x86 forth I have is C64forth :) 04:09:52 there has certainly been asm listing 04:10:15 Of a forth for cp/m-86? 04:11:30 of 8086 forth... the issue of cp/m was resolved in those days by implementing key, emit, and some sort of block i/o 04:11:44 --- nick: Soap` -> SoapSleep 04:11:54 Night SoapSleep 04:12:16 key and emit were done usually by simply setting a branch address 04:12:22 jim: Well, I'm too lazy for that much work :-) And besides, there are no programming manuals for the machine I'm talking about. 04:12:41 but there would be, for cp/m 04:13:19 Well, yes... 04:13:24 Hmm 04:13:27 the typical thing to do there was implement everything in terms of cp/m syscalls 04:13:37 Yeah, I guess so. 04:13:49 (lazy? then typing in the asm listing would be out of the question? :) 04:13:59 Yes it would. 04:14:07 The machine is an i80186 with CP/M-86 2.1 (I think), and some nice hardware. 04:14:09 but I'm sure there must be a typed in one 04:14:27 Guess so. 04:14:56 you'd probably need an assembler 04:16:06 ahh, rob_ert see you have been converting your asm to opcodes with hexeditor for nothinng! i told you there are applications to do that! ;) 04:16:30 I was worse than that when I had my imsai... 04:17:04 256 bytes of ram, no video, hand-asm on paper then keyed it in... 04:17:21 When was that? 04:17:37 1976 or so 04:17:45 Heh... 04:17:54 You must be in Chuck Moore's age :D 04:18:33 I think he's older, but I'm 43 now 04:18:52 Okay :-) 04:19:03 Unusual to see people above ~25 years on OPN. 04:19:18 me and rob_ert are not even hald of your ag.. ah. wait a second, rob_ert is not 4 years old 04:19:45 * rob_ert doesn't get that...joke. 04:20:52 being the implied age wouldn't be a bad thing 04:21:33 Well... I'm not 4. 04:21:38 More like 4^2 :-) 04:21:44 Not bad either. 04:22:44 be glad you're not 4 ^ 3 :) 04:23:19 Like Chuck Moore ;-) 04:23:35 or Draper 04:23:35 well if our ages are concatenated 04:23:40 Draper? 04:23:47 19+x = 43/2 04:23:54 x = ~ 4 04:23:57 :) 04:24:21 Who's that Draper? 04:24:37 ugh. my x boss 04:24:54 Hehe 04:25:03 but he was the one that had the first forth I ever saw... 04:25:16 Nice =) 04:25:52 he's that phone dude... 04:25:54 crunck 04:25:58 err 04:26:01 crunch 04:26:56 * rob_ert wonders what jim is talking about... 04:27:26 Captain Crunch, John Draper, my ex boss, had the first forth I ever saw 04:28:01 that was his nickname; 04:28:23 he was probably the most famous phone hacks 04:28:42 he made EasyWriter 04:29:11 What is EasyWriter? :-) 04:29:28 a word processor for the apple ][ 04:30:09 Okay. 04:30:16 reimplemented on the first IBM PC as EasyWriter Pro, the first wp for the machine 04:30:20 What CPU was that based on? 04:30:31 probably 8088 04:30:41 or 8086 04:30:43 I meant Apple II 04:30:53 6502 04:31:07 Okay. 04:31:51 same as for Ragsdale's, he wrote the fig forth installation guide based on the 6502 04:31:59 rob_ert you know what computers are based on 68010s ? :) quiz.. 04:32:29 are? :) 04:32:47 hmm :) but 68k is a nice arch 04:33:05 Heh 04:33:07 No idea... 04:33:34 amigas for insace 04:33:34 lots of regs, and they aren't warped in shape 04:33:37 a500 04:33:51 s/for insane/for instance/; 04:34:11 I don't think any macs were 04:34:15 or ataris 04:34:29 were commodores? 04:34:36 dunno 04:34:36 68010 was generally considered an improvement for embedded work, if I recall 04:34:53 no macs used them 04:35:15 * rob_ert has an A-500 :-) 04:35:23 * juu too! 04:35:24 wasn't the amiga by commodore? 04:35:28 y 04:35:29 Yes. 04:35:56 * rob_ert pets all his Commodore computers. Don't have enough room for them though :-/ 04:36:17 they seemed nice enough, I never wanted one enough to get one 04:37:20 someone has a forth as a linux kernel module... 04:37:34 Heh, nice. 04:38:18 * juu dislikes PCs 04:38:48 Warum? 04:38:58 well, intel arch is worst-case (accd'g to at least one teacher of compiler construction) 04:40:04 :-) 04:40:11 What could be done better? 04:40:20 I don't have much experience of other platforms :-/ 04:40:36 the register layout is so puzzling... 04:41:26 the instruction set isn't all that orthogonal when you put operations against processor-level data types 04:41:43 orthogonal = = 04:41:43 and pc lacks all standards, small wonder there are such as ide in existence 04:41:44 orthogonal = 04:41:46 rgrgr 04:41:53 What does 'orthogonal' mean? 04:41:57 * rob_ert can't type today. 04:42:38 oh, geometrically, in N-space, two figures are orthogonal if they are at right-angles to each other 04:44:08 * rob_ert feels stupid when he doesn't even understand the explanation of a word. 04:44:15 orthogonality in an instruction set means, vaguely, that all processor level data types can do all operations in all addressing modes 04:44:36 I see. 04:45:19 Opposed to the way things are in x86, when different registers are used for different things? 04:45:29 yeah... 04:46:01 there are some processors that have GP regs, and you can say "reg 2 is the pc" 04:46:10 Nice. 04:47:13 I am really looking forward to getting acquinted with stack-based processors myself 04:48:05 that really cuts down on the level of usually useless "generality" of > 1 operand designs 04:48:23 (such as the x86, 68k, etc.) 04:49:19 CM made this one chip, called the Novix 4000p or something like that... 04:49:23 yeah 04:50:01 4000 transistors, a data bus, an address bus, and a separate stack address bus and stack data bus 04:50:12 I plan on getting MuP21, and F21 if it ever is made available 04:50:21 Hmm... 4000 transistors? :-) 04:50:25 That's not alot. 04:50:29 rob: no =) 04:50:35 Compared to, say, a P6 ;) 04:50:49 well, consider that Novix is about 16 years old 04:50:54 but, still...quite impressive 04:51:01 yeah, they said if they were to optimize it, could reach a quarter speed of a cray :) 04:51:13 jim: I don't doubt that at all, for some reason 04:51:23 Are they cheap to produce? 04:51:35 I don't even know if they exist :) 04:51:36 (Not crays, those stackbased CPUs) 04:51:54 rob: mass-produced? hell yeah 04:52:15 :} 04:52:23 rob: if what exists? 04:52:26 Not like the $1k Intel takes? 04:52:29 err 04:52:32 jim* ;) 04:52:33 jim, if what exists? 04:52:50 rob: the estimated cost of the F21 should be roughly a $1 04:52:51 the Novix chip... did they ever make one? 04:52:58 jim: yes 04:53:03 quite a few if I recall 04:53:14 they sold a few hundred kits (I *think*, but don't quote me on that) 04:53:23 Mr. Fox bought one 04:53:51 they put about $250K into the P21's 04:54:22 and the chips, however slow and large they are now ('94 fab), still cost $25 apiece 04:54:22 Hmm... 1$... what kind of applications would it be used in? 04:54:32 rob: imo...quite a lot 04:54:35 the stacks are quite deep 04:54:43 iirc, it's pretty GP 04:55:02 I mean, will they be useful in "every-day" computers? 04:55:05 has a built-in video processor, analogue coprocessor (very nice for laboratory control interfaces), etc. 04:55:05 at one time, Jeff planned on an ethernet interface on the chip 04:55:09 rob: they could be 04:55:16 rob: I don't see why you'd want such a thing 04:55:44 Hmm 04:55:50 Since it's cheap? :-) 04:55:50 I think they are better off for applications where you want the power and flexibility of general-purpose computers at the cost and relatively simple implementation of hardware 04:55:55 as a devel env for little things with f21s in them maybe? :) 04:56:31 jim: well, most Forth-based embedded development uses the actual processor anyway 04:56:51 rather in-circuit debugging or simulation 04:57:02 so, that kind of goes with the turf (if I understood you correctly) 04:57:31 so, create a cpu/mem/IO card on (say) a pci card 04:57:46 put it in a slot and play :) 04:58:09 I'm looking forward to doing actual development using a colorForth on the F21 itself 04:58:56 Jeff said he hasn't done any production runs of F* since the first, 1998 04:59:21 I think that's what he said... it should be in the irc log 04:59:24 from what I understand, he has had at least two chip fabs 04:59:32 currently, it is on F21d 04:59:37 F20? 04:59:53 the previous one, that did not work out so well was F21c 04:59:58 and there may have been an F21b 05:00:09 all of this is at ultratechnology.com, from what I recall 05:01:01 I think it has always been called F21 05:01:15 I think the only '20 was the original P20 05:01:23 which was a disaster from what I remember 05:01:27 of hearsay :P 05:01:38 totally defunct :P 05:03:06 I'd put serious money into more fabs, if I had any 05:03:14 I really wish that was an option for me at this point 05:03:19 because I think that would be a lot of fun 05:03:51 (to have a whole bunch of the suckers in a eurorack, several monitors, and tied together by their network interface) 05:04:25 about the cost of halfway decent car :P 05:04:57 * rob_ert imagines a cluster of 1024 forth CPUs. Would be fun to play with if I knew more than I do :-) 05:05:15 rob: well, from what I can see...that is sort of the premise of Mr. Moore's 25x 05:05:27 25 x18 cpu cores in one chip 05:05:47 there was some talk of upping that anty (sp?), to 100, 500 maybe even 5000 cores 05:05:56 (ante) 05:06:02 deltab: thanks! 05:06:23 Hehe 05:06:32 Sounds nice. 05:06:36 yeah 05:06:45 All with their own stacks? 05:06:56 yes, from what I understand 05:07:03 :-) 05:07:27 About how many instructions/second can these forth chips do? 05:07:38 rob_ert it's not how many but how fast 05:07:52 you can do bloated code like in windows or efficient 05:08:05 the numbers range quite a lot 05:08:07 and even amiga program might still be faster than some windows one 05:08:37 but the numbers discussed are often placed above 2500 mips 05:08:47 and that is data several years old 05:09:13 again 05:09:21 all this stuff is listed at ultratechnology.com 05:09:30 most of it I am just paraphrasing from memory 05:10:26 but what interested me is that they were aiming for each instruction to take exactly a nanosecond to execute 05:10:44 which makes its real-time applications quite vast, imo 05:11:30 the Novix design was very interesting... an instruction word had bits set for particular things... so a smart-enuf compiler could combine words together into the same instruction, and if it reaches the ;, it sets the ; bit in the instruction and it returns after 05:11:58 jim: that's neat 05:12:30 from what I know, the Novix is an early ancestor of much of the stuff that Mr. Moore is working on now 05:12:45 (perhaps a little more ShBoom-like, if I recall, but yeah...) 05:12:53 the novix was probably the first one 05:13:02 so, I am guessing maybe a lot of that still applies 05:13:22 hmm, gotta go... bbl 05:13:31 as do I, actually 05:13:32 take care 05:13:35 nice chatting 05:13:36 =) 05:13:42 have a pleasant day, all 05:13:58 Bye. 05:14:12 take care =) 05:40:08 --- join: gforth0 (guest@adsl52101.vnet.hu) joined #forth 05:50:10 --- join: onetom_ (tom@adsl52101.vnet.hu) joined #forth 05:58:40 --- quit: onetom (Read error: 110 (Connection timed out)) 05:58:41 --- nick: onetom_ -> onetom 05:58:44 --- quit: gforth (Read error: 110 (Connection timed out)) 05:58:44 --- nick: gforth0 -> gforth 06:50:11 --- join: davidw_ (~davidw@adsl-243-109.38-151.net24.it) joined #forth 06:50:11 --- quit: davidw (Read error: 104 (Connection reset by peer)) 06:50:33 --- nick: davidw_ -> davidw 06:51:54 --- nick: juu -> juuAway 07:25:51 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 07:34:39 --- nick: juuAway -> juu 07:34:47 hey 07:34:48 Hej juu. 07:41:54 this Murray dude is off the hook 07:42:12 pretty seriously, it would seem 07:42:41 ? 07:44:29 read comp.lang.forth 07:45:09 davidw: what sw do u use 4 reading it? 07:45:11 google? 07:45:21 onetom: I use emacs' gnus 07:45:31 oh :)) 07:45:32 and connect to the news server of my provider 07:45:43 google works too, if you don't mind web interfaces 07:46:11 and what would u do i u wanna read a fat thread 07:46:25 uve found via google? 07:50:07 if I need to search, yes, i use google 07:50:41 but if uve found... 07:50:51 who would u download it into emacs? 07:51:19 whats new on clf anyway? 07:51:32 onetom: that Murray dude 07:51:42 no, if I am just searching, I read it with google 07:51:56 if I am just reading the newsgroup, I read it with gnus 07:52:21 but how would u do such a thread dl? 07:52:26 is it possible @ allt? 07:52:28 all? 07:52:31 I don't think so 07:52:35 I just read it via google 07:52:57 how do u limit the number of msg in emacs? 07:53:12 it has an automatic limit 07:53:16 I think 07:53:20 if not, you set it 07:53:42 c c :/ 08:01:32 hmm.. 08:01:41 * juu is browsing irc-galleria 08:01:46 it's place where there are finnish irccers photos 08:01:52 hah, 3 million hits every day 08:02:28 (Figures in parentheses refer to the 7-day period ending 14-May-2002 14:15). 08:02:30 Successful requests: 413,944,050 (21,408,133) 08:03:33 Data transferred: 4.270 terabytes (170.188 gigabytes) 08:03:33 Average data transferred per day: 11.816 gigabytes (24.312 gigabytes) 08:05:04 not bad 08:05:08 for one server oly 08:05:10 only 08:14:52 --- join: GilbertBSD (~gilbert@max1-1.dacor.net) joined #forth 08:15:01 re 08:15:12 hi 08:18:17 Hi :) 08:18:28 hej. 08:18:31 wie Gehts? 08:24:50 Gut, danke. 08:24:54 Und mit dir? 08:25:06 zehr gut. 08:25:09 :D 08:25:44 reaction time: 3 days and 2 nights. 08:25:48 A record! 08:26:16 sehr gut* 08:26:44 rob_ert: Ich habe ein 'strong accent' :D 08:26:53 Ja, das höre ich. 08:27:22 der Strunger Accenter Engeblatzenfurter wie Dorkensprekunkel 08:27:50 Genau... 08:28:16 I can't find my german-english dictionary so I will let that pass for now. 08:28:25 =D 08:28:36 Well, you're lucky 08:28:49 Since you speak english, you have all those online dictionaries. 08:29:10 I don't feel like 1. looking for a dictionary. 2. Using it 08:29:26 GilbertBSD we notice that 08:29:56 I can't mark the online dictionary all over! 08:30:07 I can mark mine as much as I want and do other things with it. 08:30:25 GilbertBSD: just use 'dict' 08:30:29 dict cur 08:30:38 dict cur? 08:30:49 dict word 08:30:52 dict this dict that 08:30:54 Wo? 08:30:55 dict is good 08:31:14 > dict 08:31:14 dict: Command not found. 08:31:14 > 08:31:20 dict 08:31:28 so much for bsd 08:31:36 har har har har! 08:31:54 murr 08:32:11 you could probably install the port 08:32:22 Si signor 08:33:36 ecco, bravo 08:34:51 davidw: I think I know why there are more implementations of forth than libraries FOR forth 08:35:12 NIH 08:35:22 NIH? 08:35:33 Not Invented Here 08:35:49 the tendency of techies to want to build their own, instead of using someone else's 08:35:53 more or less ... if that means "this is not a good enough implementation" 08:36:03 nah 08:36:07 that's a bunch of bullshit, mostly 08:36:08 there is no one ULTIMATE forth. 08:36:16 but there are a lot of good ones 08:36:29 surely ... one of the better ones works only in dos . 08:36:37 but not in linux or on any other platform. 08:37:08 its name is fpc 08:37:13 Even CM used it once ;) 08:37:24 chuck "portability doesn't exist" moore 08:37:30 that dude lost the plot 08:37:54 yes he had some reason for saying that... I forget. 08:38:12 because he's not in tune with modern software? 08:38:25 "hardware is so fast that it can do anything instantaneously" 08:39:20 I don't think his elevator stops on all floors anymore. over. 08:39:39 :D 08:39:49 I have a rough solution... 08:39:57 bungee jump! 08:39:59 yaay 08:40:00 good idea 08:40:01 :) 08:40:16 GilbertBSD: to what? 08:40:25 the whole debacle. 08:40:38 * davidw logs into www.apache.org 08:40:43 A complete primitive set with the addon words as a library. 08:40:52 no stay here man. 08:41:59 libraries are the most sensible way of doing things 08:42:09 but are they really? 08:42:15 yes 08:42:22 if you are missing them they tend to be quite the pain. 08:42:31 davidw: have you taken a look at rebol yet? 08:42:42 no, it's some proprietary wierd thing, afaik 08:43:02 yes indeed... but you should really take a look at it sometime. 08:43:11 what's so good about it? 08:43:19 I just don't believe in miracle scripting languages 08:43:24 it is pretty small, packs a gui, a set of network protocols, and it was created by a forther 08:43:26 the best one out there is probably elastiC 08:43:45 just the concept not anything else. 08:43:57 www.rebol.com and www.rebol.org 08:44:25 seems hokey-dokey to me 08:44:42 have you seen it yet? 08:46:01 I'm looking at it 08:46:47 you could probably do a lot of that in Tcl 08:47:08 yes indeed... 08:47:19 but you won't have to get ALL Tcl interpreters to do that. 08:47:41 hrm? 08:47:50 just distribute your code as a tcl library 08:48:14 but with this EVERYTHING comes in one package! 08:48:38 the gui bits are quite TCL ish but not that much so.. 08:48:50 I digress. 08:48:55 so you have one bloated package instead of smaller packages 08:48:59 you can do that in tcl if you want 08:49:10 davidw it is not bloated is my whole point! 08:49:36 well, there has to be some tradeoff 08:49:46 ummm try it man. 08:49:56 why is it small? what is he throwing out? 08:50:00 elastiC is C 08:50:07 davidw: it is inextensible ... 08:50:12 also it is not open. 08:50:27 or better yet, extensibility is not that easy. 08:50:38 in what? rebol? 08:51:02 yes in Rebol 08:51:13 unlike forth or sheme or lisp or logo etc 08:52:35 languages that are difficult to extend are worthless 08:52:51 what's it written in, anyway? C? 08:53:21 I dunno what it is written in. 08:53:45 but there aren't that many extensible languages in existence... yet they do their jobs just fine. 08:54:04 Another digression. 08:54:14 I think rebol is forths future. 08:54:34 or if I knew whatever the heck I was doing, it would be a very rebolly forth. 08:54:52 it's not a bad looking language.... basically, it's a ripoff of Tcl 08:55:00 which is a very nice language 08:55:02 bah. 08:55:06 I dun like TCL 08:57:09 why not? 08:57:21 I prefer python. It has an elegance ... 08:58:26 tcl is more forthy... it's extensible 08:58:46 I bought the TCL book but only because of TK 08:58:51 I still haven't read it. 09:01:07 what are some nice TCL things? 09:01:35 simple, easy, extensible, has usefull stuff built in, widely used 09:03:26 I find python simple, easy, it has useful stuff built in, and it is widely used. 09:03:48 python's not bad at all 09:03:55 I rather like it, actually 09:04:47 I think some sort of next generation tcl would be cool 09:04:56 tcl has a little more cruft than I care for, in some regards 09:05:09 the core is really beautifully coded, though 09:05:17 I could never produce code that nice 09:05:23 the C code is a pleasure to read 09:05:26 copy and paste my man. 09:05:34 what about tk? 09:05:46 tk is a good idea, but it's crufty:-/ 09:05:59 it's still super useful 09:06:06 why do you call it crufty? 09:06:09 it could stand a good cleanup though 09:06:12 it is one of the nicest parts of tk! 09:06:17 it's got a lot of X based stuff in it 09:06:24 I don't really like that 09:06:30 what do you want then? 09:06:35 how would it talk to X? 09:06:46 via xlib 09:06:49 like everything else 09:07:06 but what I'm saying is that even the windows and mac versions need some of the X includes... 09:07:11 which are included in the distribution, of course 09:07:16 but... do you see what I'm saying? 09:07:31 of course, the end user doesn't see that, really 09:07:36 yes... 09:07:37 it's a very nice package, all things considered 09:07:43 they don't need the X includes is what you are saying. 09:07:52 a forth/tk won't be bad at all. 09:10:00 tk is also, apparently pretty tied to tcl 09:10:04 which isn't good either 09:10:16 as much as I like tcl, there isn't much reason to tightly couple them 09:10:27 but tk came with tcl ... if anyone wanted an untied tk, well they can code their own! 09:10:59 yeah, but that's small minded thinking 09:11:16 tk would be a much more used toolkit if people didn't have to bundle it with tcl 09:11:23 when you make a forth/tk 09:11:29 you will have to link in the tcl library 09:11:49 Needed an independent TK named Teekay 09:13:31 can you rewrite TK ? 09:14:03 uh, sure, if you give me a lot of time and pay me for it 09:14:27 but I thought you had both! 09:14:38 Long lunch breaks and time :D 09:15:33 I do, but I have other stuff to do 09:15:37 some of which I get paid for 09:16:20 what does CM want us to use colorforth for? 09:17:06 I have no idea 09:17:21 going insane trying to use the 'editor' with the conveniently remapped martian keyboard 09:18:08 you know the aliens from the simpsons? with the helmets and tentacles? I could see them using something like cforth 09:18:44 bah. 09:18:57 I can't understand forth yet. 09:19:01 I must be pretty dumb. 09:19:09 you understand python ok? 09:19:22 yes ... but I can't convert stuff from python to forth. 09:19:43 I think it's more indicative that forth isn't really that logical in some ways 09:19:53 well, it's logical, but... not intuitive 09:20:05 --- quit: onetom (Read error: 110 (Connection timed out)) 09:20:11 did you catch chucks' quote about how giving variables names was a bad idea? 09:20:19 yes I did... 09:20:23 --- quit: gforth (Read error: 110 (Connection timed out)) 09:20:25 he said the stack took care of all of that. 09:20:32 I think that's a bunch of bullshit, myself 09:20:37 nameless something he called it. 09:20:53 yeah, well, the problem is that there IS a value you are trying to keep track of 09:21:04 but in addition, you have to try and follow it around on the stack 09:21:35 he says the stack shouldn't be more than 4 deep. 09:21:58 I'm not much of a forth programmer, so part of it is my fault 09:22:05 but still... I don't buy his logic %100 09:22:22 WTF..some pusswad sent me what looks to be a 1 meg email 09:22:36 ah, my uncle 09:22:39 grr 09:22:56 hahahah 09:23:02 it is prolly an attachment 09:24:15 hehe, he's pretty cool 09:24:23 at 40 something, he's still racing motorbikes offroad 09:25:15 Cool uncles Rule! 09:26:23 --- join: onetom (tom@adsl52043.vnet.hu) joined #forth 09:27:09 damn, I want to resume work on pforth + ecos 09:27:23 it's pretty cool 09:27:36 I want to see if I can make irq handlers in forth 09:27:46 davidw: on what arch? 09:27:50 I'm having some troubles though getting it to grok my irq handlers 09:28:00 onetom: well, I'm using an i386 to fool with 09:28:08 but the cool thing is that ecos runs on lots of chips 09:28:21 so my system is portable 09:30:03 davidw: hmmm.. sounds exciting... 09:30:15 davidw: does it have tcpip? 09:30:29 you can add that in if you want 09:30:36 it's a very modular OS 09:30:42 it's meant for deeply embedded applications 09:30:58 binding forth to it seems logical to me 09:31:02 davidw: i will chk it, nowdays then 09:31:18 forth would be kind of painful to use as a shell in anything but a deeply embedded system 09:31:20 aha, thats sounds reasonable 2 some extent... 09:31:47 well.. i dont agree w that 100% 09:32:03 no? you could use forth as a replacement for /bin/sh ? 09:32:09 I would shoot myself, I think 09:32:12 but never though of the shape of the forth as a shell 09:32:41 but bigforth does it, eg ?p 09:32:44 :p 09:33:02 maybe I just don't think forthy enough 09:33:12 how would you do like ls -l foo*.gif 09:33:29 yeah how would you? 09:33:30 just like that ithink :) 09:33:40 but wait, & im gonna test it 09:34:00 davidw: do you know what the absolute forth to the metal words are? 09:34:13 the primitives of primitives for forth. 09:34:31 davidw: yeah, that worx 09:34:45 onetom: how ?! 09:34:50 see ls 09:34:51 : LS 09:34:51 SCANOPT DUP 09:34:51 0= IF DROP DROP S" *" THEN 09:34:51 65 -OPT? 128 AND 68 -OPT? 256 AND OR -ROT (DIR ; 09:35:14 GilbertBSD: uh... hrm... not really 09:35:18 davidw: try bigforth! 09:35:29 davidw: it compiles flawlessly under linux 09:35:31 bigforth looks like yaiof 09:35:34 it's not available on ppc 09:35:45 davidw: he? 09:35:53 it's i386 only 09:35:57 ppppttttthttt 09:36:10 ahhaa, c. thats sad :/ 09:36:14 yep 09:36:28 so, I don't really understand that code, but... * seems to be special 09:37:27 how do you forward scan in forth? 09:37:28 it must b the default file parameter iguess 09:37:30 ls -l 09:37:35 -l is not the command, but ls is 09:39:43 fucking gforth docs 09:41:01 [06:00] akkor miért nem forthban fejlesztenek kernelt és nem c-ben ? 09:41:07 whoops 09:41:35 hehe always :) 09:41:45 yees yeess 09:41:47 * juu was given 1970 basic school book 09:42:06 sorry 4 being so miserable 09:42:54 I guess I don't get create does> 09:43:20 Niether do I :( 09:43:24 * rob_ert wants to! 09:48:22 onetom: so can you explain it? 09:52:05 gforth's docs are buggered 09:52:23 --- join: futhin (thin@h24-64-175-61.cg.shawcable.net) joined #forth 09:52:29 Hey futhin 09:52:36 what's up 09:52:47 Explain does> for davidw :) 09:54:03 ok, when you CREATE a word, the word is entered into the dictionary 09:54:40 and then you use DOES> to put the code into the word's code space in the dictionary 09:54:58 a word in the dictionary looks like 09:55:06
09:55:09 09:55:19 so does> puts the code into the place 09:55:29 and when the word is called 09:55:36 the code inside there gets executed 09:55:45 so what's a concrete example 09:56:18 CREATE TEMPWORD DOES> ." hello world" 09:56:21 tempword 09:56:25 i dunno, something like that 09:56:31 not completely sure 09:56:36 because i haven't really used DOES> yet 09:56:37 lets ask g4 09:56:46 g4 create tempword does> ."hello world" 09:56:55 One question: do most 16-bit x86 forths use different segments for headers/code? 09:56:56 sif: does> 09:56:57 futhin: Word not found: does> 09:57:04 sif: create tempword 09:57:05 futhin: 09:57:06 g4 create tempword does> ." hello world " 09:57:12 g4 tempword 09:57:22 gil: gforth isn't here 09:57:24 gforth isn't here 09:57:27 can't notice that? :P 09:57:27 Hehe 09:57:33 onetom: 09:57:37 are you hiding g4? 09:57:40 onetom isn't here 09:57:41 god 09:57:44 what client do you use? 09:57:48 my eyes 09:57:58 he's here, nevermind 09:58:11 i meant gforth :P 09:58:14 Yes I know he is here. 09:58:19 futhin: your example doesn't work 09:58:25 hasty conclusiions it is called Futhin. 09:59:08 gilbertbsd: you should've noticed g4 wasn't there when i first tried g4, before you did 09:59:23 damn housemate's alarm is going off 09:59:24 I hate that 09:59:35 davidw: yeah, there's something to end the DOES> 09:59:51 I hit enter after you hit enter. 09:59:54 need to encapsulate the code with DOES> and something else.. i forget 09:59:59 and I thought g4 was just being slow. 10:00:42 gil: you didn't hit enter after i hit enter.. i typed stuff to sif, rob_ert spoke 10:00:56 in the interval 10:01:02 first came your line to g4 ... 10:01:15 then came my line to g4 ... to g4, i hit enter after you hit enter. 10:01:16 [10:57] g4 create tempword does> ."hello world" 10:01:16 [10:57] One question: do most 16-bit x86 forths use different segments for headers/code? 10:01:16 [10:57] sif: does> 10:01:16 [10:57] futhin: Word not found: does> 10:01:16 [10:57] sif: create tempword 10:01:17 [10:57] futhin: 10:01:19 [10:57] g4 create tempword does> ." hello world " 10:01:19 this is illy anyway. 10:01:32 fuck 10:01:34 this makes no sense 10:01:51 Hehe 10:01:58 davidw: yeah don't worry, i probably fed you false info 10:02:15 time for me to go test gforth 10:02:18 and I thought g4 was just being slow. 10:02:21 I rest my case. 10:02:29 onetom: where is g4? 10:03:35 davidw: it works for me 10:03:38 i did 10:03:38 GilbertBSD: its just a shortcut 4 gforth: 10:03:47 yes where is gforth? 10:03:59 GilbertBSD: oops, sorry, not what but where 10:04:12 davidw: i did: create tempword does> ." hello world" ; 10:04:16 and then typed tempword 10:04:20 GilbertBSD: i rebooted my server some mins b4 10:04:21 and it displays hello word 10:04:55 create tempword does> ." hello world" ; ok 10:04:55 tempword hello world ok 10:05:21 and now you can see does> is a very simple mechanism and very simple to understand 10:05:34 and i don't have a clue how anybody can have trouble understanding it 10:05:36 : create-person create does> ." Hello, there!" ; ok 10:05:37 create-person robert ok 10:05:37 robert Hello, there! ok 10:05:38 :-) 10:05:50 --- join: gforth (guest@adsl52043.vnet.hu) joined #forth 10:05:55 gforth: :D 10:05:58 rob_ert: in file included from *the terminal*:-1 10:05:58 rob_ert: /tmp/fsock-sh-server.request.tmp:46: Undefined word 10:06:00 rob_ert: :D 10:06:01 yeah that is another way to use does> 10:06:01 Hehe 10:06:02 rob_ert: ^^ 10:06:04 rob_ert: Backtrace: 10:06:10 using does> inside a word is nifty 10:06:13 g4 create tempword does> ." hello world" ; 10:06:19 g4 tempword 10:06:22 GilbertBSD: in file included from *the terminal*:-1 10:06:22 GilbertBSD: /tmp/fsock-sh-server.request.tmp:46: Undefined word 10:06:22 GilbertBSD: tempword 10:06:22 GilbertBSD: ^^^^^^^^ 10:06:22 GilbertBSD: Backtrace: 10:06:27 You can't do that... 10:06:46 I can't do that or g4 won't let anyone? 10:06:51 gforth: create tempword does> ." hello world" ; tempword 10:06:54 futhin: hello world 10:06:55 Only one line at the time 10:07:29 hmmm I thought create inserted the word tempword into the dictionary permanently. 10:07:37 there isn't much of a difference between that and 10:07:44 onetom changed gforth 10:07:49 : tempword ." hello world " ; tempword 10:07:50 it doesn't remember anything 10:07:54 yeah 10:07:56 10 var robbe ok 10:07:56 robbe . 10 ok 10:07:58 the create blah blah is longer. 10:07:59 er 10:07:59 how about this: 10:08:03 : var create here ! does> @ ; ok 10:08:06 That was cool :-) 10:08:11 : foo create does> + ; 10:08:15 foo bar 10:08:17 gilbertbsd: you use does> inside a word and the word can create words.. it's useful 10:08:18 3 4 bar 10:08:25 now what is on the stack? 10:08:39 7 10:08:40 futhin: I thought that was already possible. 10:08:50 futhin: *wrong* 10:08:51 heheeh 10:09:01 heh 10:09:20 gil: yes it is, thru does> !! 10:09:43 you use does> inside a word and the word can create words.. 10:09:54 perhaps your explanation is a bit vague or I am dense. 10:09:55 g4 : foo create does> + ; foo bar 3 4 bar . 10:09:58 futhin: 1075038412 10:09:59 Since I am not dense .... 10:10:09 g4 : foo create does> + ; foo bar 3 4 bar @ 10:10:29 sure, i'm not trying to create a clear explanation 10:10:38 but you are a little dense anyways so don't worry :P 10:10:42 well what about a clear one? or is that too much to ask? 10:10:48 futhin: I resent that! 10:10:49 g4 : foo create does> + ; foo bar 3 4 bar @ . 10:10:52 futhin: -24395848 10:10:59 haha 10:11:05 rob: :) 10:11:08 GilbertBSD: it seems he's a little dense too 10:11:23 is simplicity not the whole point of Forth? 10:11:23 How can I write code to the newly created word? 10:11:35 not going to bother with a clear explanation, i'm leaving soon and driving for 8 hours 10:11:46 Hehe 10:11:52 There are lots of pages about that 10:11:54 so a clear explanation is harder! Now why didn't you just say so? 10:12:00 editors note: "I don't know what I'm talking about, fully" 10:12:02 http://zetetics.com/bj/papers/moving3.htm 10:12:09 http://home.tampabay.rr.com/jforth/C06_Tutorial_Advanced.html 10:12:35 gilbert: the simplest, clearest explanation is the hardest, for anything.. everybody knows this 10:12:45 gilbert: there's a saying "it takes a genius to be simple" 10:12:54 well, dinner time 10:12:55 bye 10:12:57 bye 10:13:01 so you are not a genius... 10:13:03 I thought ... 10:13:05 I ... 10:13:06 :( 10:13:21 i'm a genius, if i try to be simple ;P 10:13:30 right now i'm not trying to be simple so i guess not :P 10:13:38 but are you a genius if you don't attain simplicity ? 10:13:43 ah good. 10:14:14 i think i aim to achieve simplicity over my life.. i want to improve processes and systems, by simplifying them and finding better solutions 10:14:18 what forth needs then is a Genius. 10:14:33 chuck moore is a genius 10:14:40 he is obscure. 10:14:42 obviously he strives to simplify 10:14:55 and his speaking is very terse and very simple.. 10:15:26 yes, he's a little obscure.. 10:15:30 not really a good thing 10:15:47 there are different areas to be a genius in.. 10:15:51 or abstruse 10:15:51 ANd 10:15:51 : new create here ! does> @ execute ; ok 10:15:51 rather than or. 10:15:51 : robert ." Hello there!" cr ; redefined robert ok 10:15:51 ' robert new person ok 10:15:51 person Hello there! 10:15:51 Cool :-) 10:15:52 Wonder how valid that is though ;) 10:16:18 Forth needs a Genius spokesman 10:16:25 true true 10:16:33 a communicator 10:16:43 somebody who can convey the ideas of forth in the best possible way 10:16:49 and keep it clear and simple 10:16:56 If I knew forth well enough, I would be happy to be its spokesman 10:17:12 leo brodie came a little close, but not close enough.. and the stuff needs to be available on the internet 10:17:14 Learn it =) 10:17:14 alas ... python and scheme are tugging ever harder ... 10:17:32 rob_ert: to be absolutely clear with forth, I still see the need for asm 10:17:39 so asm is it .. forth has to wait. 10:17:39 bah 10:17:45 Hehe 10:17:48 Learn asm :D 10:17:49 NOW! 10:17:50 you don't really need to know asm to understand forth 10:17:54 Well 10:17:55 and to code many things in forth 10:17:56 Hrm 10:17:59 Right. 10:18:04 but i recommend 10:18:07 But it's good to know it anyway 10:18:17 so ASM is it. 10:18:26 "assembly language step-by-step second edition" by jeff duntemann best book for asm out there! 10:18:34 costed 75 bucks canadian.. 10:18:36 yes I got a copy recently. 10:18:45 ah, cool 10:18:56 is that the only necessary asm book? 10:19:06 sure 10:19:17 if you get into assembly programming deeper 10:19:26 you'll want a reference manual 10:19:29 BTW it seems the contents of duntemann are adequately covered by Pertzold in "code' 10:19:30 and other stuff 10:19:35 you should take a look at it. 10:20:04 with the book by duntemann the information was really easy to absorb 10:20:14 was that your first asm book? 10:20:14 so that's the main thing i liked about it 10:20:17 no 10:20:22 :| 10:20:25 i tried reading 5 other asm books before 10:20:29 but they all sucked crap 10:20:31 so you had an idea. 10:20:34 no 10:20:38 jeez 10:20:39 trust me 10:20:41 when i say 10:20:55 jeff duntemann's book is _great_ and is the best first book to read 10:21:08 and will give you enough knowledge, background, etc to understand assembly 10:21:13 futhin: get a copy of code by pertzold sometime. 10:21:24 I highly recommend it. 10:21:39 is code by pertzold well written? easily absorbable? can i read the whole book in 4 hours without having to think?? 10:22:05 read duntemann.. don't hesitate 10:22:10 read the first chapter tonight 10:22:18 anyways 10:22:20 i gotta go 10:22:31 so ta ta for now 10:22:33 and yes my recommendations count. 10:22:44 --- quit: futhin ("ttyl") 10:23:07 yes you can read the whole book without having to think. 10:23:15 Assuming you can read. 10:27:46 --- quit: GilbertBSD ("xchat exiting..") 11:02:17 --- join: GilbertBSD (~gilbert@m175.max3.dacor.net) joined #forth 11:03:10 rob_ert: 11:06:08 rob_ert: www.mises.org ... if you get around to it :D 11:06:09 Yes, sir? 11:06:14 * rob_ert checks 11:06:22 * GilbertBSD waits for it 11:06:34 btw, does> is nice :) 11:06:39 bah 11:06:45 I am done with forth. 11:06:59 I am going to learn ASM and scheme. 11:07:04 "relative to families in the United States, Swedish family income is considerably less." 11:07:11 :D 11:07:18 Should that be supposed to be new? 11:07:18 We make more $$$ here man. 11:07:24 Totally. 11:07:35 We have lower gaps between the classes though. 11:07:43 there are no classes here. 11:07:47 pff 11:08:00 Less stinking rich and less really poor people here. 11:08:13 But that's slowly changing, it seems :-/ 11:08:22 Fewer stinking rich and fewer dirt poor. 11:08:31 or filthy rich and dirt poor. 11:08:49 --- join: oink (~ziga@owl.cuckoos.net) joined #forth 11:08:51 Thanks, mr. English teacher ;) 11:08:54 But you get what I mean 11:08:56 Hi oink. 11:08:56 heya :) 11:09:06 Hmm 11:09:15 Should I do my homework or play more with forth? :D 11:09:18 Yes Mr. .se Teacher, I get what you mean. 11:09:27 do you homework, and come back :D 11:09:28 rob_ert: abandon forth and play with asm instead. 11:09:30 your * 11:09:48 GilbertBSD: I've done that for years. 11:10:13 Forth is still new an exciting :) 11:10:19 blah. 11:10:26 :-) 11:10:52 I am rather dissapointed in forth... superb ideas, but until I learn asm, I am not coming back. 11:11:02 Why dissapointed? 11:11:20 too many things to get into.. 11:11:21 GilbertBSD better pick up good asm tutorial then :) 11:11:25 aoa 11:11:28 for example 11:11:34 I have a great asm book thank you. 11:11:48 disappointed* 11:11:52 Hehe 11:12:13 Well, from an assembly programmer's point of view, forth is really a neat thing. 11:12:20 see I went to the lisp room and they said 'learn forth' I came to the forth room and they said 'learn asm' 11:12:32 so since I can't get any lower than that ... 11:12:35 Asm it is. 11:13:00 Haha ;D 11:13:19 so i go then from ASM to scheme to lisp to prolog then smalltalk 11:13:29 I tell everyone they should learn asm, so they'll understand HLLs better... 11:13:30 much much later on, I will pick up forth again. 11:13:39 tell them to read SICP 11:13:40 Hehe 11:13:45 And that is? 11:16:39 ... google sicp 11:16:50 I gtg 11:16:56 or you can do /msg abi sicp 11:17:05 Huh? 11:17:07 Oh 11:17:07 yes much better 11:18:28 n e way ... don't abuse abi 11:18:32 bye 11:18:34 --- part: GilbertBSD left #forth 11:18:43 --- quit: tathi ("leaving") 11:26:28 --- nick: juu -> juuBBL 12:20:34 --- nick: juuBBL -> juu 12:30:06 --- join: gforth0 (guest@adsl52005.vnet.hu) joined #forth 12:32:16 --- join: GilbertBSD (~gilbert@m129.max3.dacor.net) joined #forth 12:34:22 --- nick: GilbertBSD -> latest 12:34:44 --- nick: latest -> latestonion 12:35:19 --- part: latestonion left #forth 12:44:32 --- join: onetom_ (tom@adsl52005.vnet.hu) joined #forth 12:47:35 --- quit: gforth (Read error: 110 (Connection timed out)) 12:47:35 --- nick: gforth0 -> gforth 12:48:41 --- quit: onetom (Read error: 110 (Connection timed out)) 12:48:42 --- nick: onetom_ -> onetom 12:52:21 --- quit: SoapSleep (Read error: 113 (No route to host)) 13:27:13 --- quit: juu ("murr sanoo karhu") 14:03:58 --- join: Etaoin (~david@ljk26.sat.net) joined #forth 14:04:27 Hello. 14:04:34 hi 14:37:30 anyone know the name of the ANS version of LATEST or LAST? 14:38:06 no 14:45:20 looks like LATEST is what's accepted but I can't find it in the ANS listings :/ 15:29:37 --- quit: rob_ert ("Nothing is real.") 15:30:10 --- join: gforth0 (guest@adsl52004.vnet.hu) joined #forth 15:43:13 --- join: onetom_ (tom@adsl52004.vnet.hu) joined #forth 15:46:42 --- quit: gforth (Read error: 110 (Connection timed out)) 15:46:42 --- nick: gforth0 -> gforth 15:47:41 --- join: MrReach (~mrreach@209.181.43.190) joined #forth 15:48:10 --- quit: onetom (Read error: 110 (Connection timed out)) 15:48:10 --- nick: onetom_ -> onetom 15:48:13 is there a homepage for isForth??? 15:48:47 MrReach: /topic 15:50:35 DUH! 15:50:38 thanks! 15:50:55 :) np 16:06:42 --- join: I440r (~mark4@1Cust185.tnt1.bloomington.in.da.uu.net) joined #forth 16:12:06 good night:D 16:14:54 --- join: Soap` (flop@210-55-151-166.dialup.xtra.co.nz) joined #forth 16:15:37 mrreach ltns ;) 16:15:37 heh 16:25:55 hihi 16:26:13 won't be here too much longer, have to go down to the shop later 16:26:19 heh 16:26:28 when I actually own it, I might log in there to chat 16:26:34 or might not 16:26:36 wanna see the code i came up with when i couldnt find yours ??? :) 16:26:49 certainly 16:27:06 you decided how Anton Ertl did 16:27:13 : struct: ( --- a1 ) 16:27:13 0 constant \ create named structure 16:27:13 here 4- \ remember body field address 16:27:13 0 ; \ current size of structure 16:27:23 : field: ( n1 n2 --- ) 16:27:23 over const \ create named structure field offset 16:27:23 + ; \ keep total structure size 16:27:29 I chose to use a memory struct, rather than the stack 16:27:34 : ;struct ( a1 n1 --- ) 16:27:34 swap ! ; 16:27:58 use the stack in the say way if/else/then 16:27:58 ya 16:28:37 the thing is. i used exactly the same names you did i think 16:28:46 so your code MUST have been sitting in the back of my mind all along heh 16:28:52 similar names 16:29:12 I used a double DOES> construct that would have set your teeth on edge 16:29:30 the code is identical enough that i credited you in the source, called it YOUR code not mine 16:29:38 oh, ok 16:29:40 no 16:29:40 i use does> alot! 16:29:50 does> is one of my favourite words! 16:30:09 --- join: gforth0 (guest@adsl52022.vnet.hu) joined #forth 16:30:11 im just not using it in the kernel itself very much 16:30:11 however. 16:30:18 check out the definition for const 16:30:25 : word create ... does> ... create ... does> ... ; 16:30:34 its a does> word 16:30:49 err now THAT i cant understand 16:30:57 create foo does> does> foo 16:31:04 its a word that creates creating words 16:31:05 thats anothyer one lol 16:31:17 yes 16:31:23 something like ... 16:31:34 const is a word that creates creating words and it uses only one does> 16:31:38 1 field-type: bytes 16:31:45 2 field-type: words 16:31:58 4 field-type: dwords 16:32:02 4 field-type: cells 16:32:17 40 bytes client-name 16:32:22 heheh - you used cells :P 16:32:31 i havent defined those 16:32:42 yes, the above was in courtesy to yu 16:33:15 but i think ppl using these would appreciate them 16:33:27 yes - i figured that :) 16:34:03 I chose memory records because eventually I hope to have a syntax that is a melding of gforth syntax and VFX syntax, which includes substructs, unions, and all kinds of neat stuff 16:34:51 i was thinking of putting something like aums string stuff in isforth 16:34:59 ." %s %d %s" 16:35:08 like in c 16:35:11 I'm not at all familiar with it, so can't really comment 16:35:18 ugh 16:35:24 ah! ok, substitutions 16:35:27 dio lazzarone 16:35:38 what am i DOING to forth! 16:35:38 lol 16:35:54 actually, Speuler and I sat down one night and wrote out a rather complete string spec 16:36:01 yes 16:36:10 it would slow string output down tho 16:36:23 so i might have ." and %." 16:36:38 it used a "descriptor" and a "string memory", similar to the way the old MSBasic did internally 16:36:51 i think you showed it to me a long time ago but i didnt have any way to use it back then 16:37:24 it actually ended up looking quite versatile, though I never got it written because of a hard drive crash 16:37:46 well i never used msbasic hehe 16:37:57 it sucked 16:37:57 and would never admit publically if i had :) 16:38:15 but it worked, and the string handling was the most advanced part of it 16:38:39 (how it stored strings internally, that is) 16:39:40 in any case, the descriptor held an address and a length ... the string itself was stored elsewhere 16:39:42 counted strings are a HELL of alot better than ascii z 16:39:51 with an ascii z string you dont know how much data you have 16:40:14 both the descriptor and the string could be in either the dictionary or in allocated memory 16:40:37 fpc stored strings seperatly didnt it ? 16:40:49 don't remember 16:41:05 what I wanted was for web page scripting 16:41:55 when compiling the prog, I wanted to build enourmous strings incrementally, then save them into the executable, then dump them out at run-time with minimal handling 16:43:20 --- join: onetom_ (tom@adsl52022.vnet.hu) joined #forth 16:43:44 enormous strings = web page ? 16:43:50 yep 16:43:51 --- quit: onetom (Read error: 110 (Connection timed out)) 16:43:52 --- nick: onetom_ -> onetom 16:44:20 or header and footer as static strings braced around dynamic content 16:44:33 --- quit: gforth (Read error: 110 (Connection timed out)) 16:44:34 --- nick: gforth0 -> gforth 16:47:08 i added a new word to isforth thats much like the ? : construct in c 16:47:18 ?: true-word false-word 16:47:27 as a replacement for if/else/then 16:47:48 * MrReach nods 16:47:53 i was using 0= 1 and exec: in so many places 16:47:59 heh, another damn parsing word @:^> 16:48:02 0= abs exec: 16:49:22 no 16:49:29 actualy 16:49:37 ?: just compiles (?:) 16:49:46 then true-word and false-word are compiled normally 16:50:35 ?: t f blah blah 16:50:35 executes either t or f then continues with blah blah 16:52:24 oh ... 16:52:40 so it fetches the xts following it in the dictionary??? 16:53:12 im not scared to use parsing words but they are more clumsy 16:53:12 yes 16:53:46 yes, and a break in "regular syntax 16:53:53 ok, time for me to go 16:54:05 thanks for the compliments about the strcts package 16:54:06 the same way exec: does 16:54:06 exec: doesnt compile everything that follows it hehe 16:54:18 exec: foo bar baz bam blah 16:54:18 forth does 16:54:30 --- nick: MrReach -> MrGone 16:55:14 it deserved them heh 16:55:19 its GOOD forth! 16:55:25 small. neat. no mess 16:55:49 and very very in line with what i want for isforth 16:56:01 isforth compiles all the elements of the structure as consts which are compiled as literals 16:56:06 and will eventually be dumped on turnkey 16:56:25 so the expense of having a gazilluon #define type things is next to nothing! 16:56:49 2 const AF_INET 16:57:13 think of 2378658245768=5548 more consts you want and define them. those you dont use wont take up ANY space in your target 17:12:17 --- join: Soap- (flop@210-55-151-166.dialup.xtra.co.nz) joined #forth 17:12:20 --- quit: Soap` (Read error: 104 (Connection reset by peer)) 17:29:06 --- quit: davidw (Read error: 113 (No route to host)) 17:30:06 --- join: gforth0 (guest@adsl52021.vnet.hu) joined #forth 17:43:32 --- join: onetom_ (tom@adsl52021.vnet.hu) joined #forth 17:46:15 --- quit: onetom (Read error: 110 (Connection timed out)) 17:46:16 --- nick: onetom_ -> onetom 17:46:30 --- quit: gforth (Read error: 110 (Connection timed out)) 17:46:31 --- nick: gforth0 -> gforth 18:21:08 --- join: Blandest (~Bland@h24-65-137-230.ed.shawcable.net) joined #forth 18:21:53 greetings. 18:22:42 --- join: CrowKiller (Vapo_Rulez@cnq5-233.cablevision.qc.ca) joined #forth 18:22:49 hi 18:24:15 hi CrowKiller 18:24:16 hi 18:24:23 hi bland 18:24:28 hey 18:24:31 at what time chuck will be there tommorow? 18:24:32 are you new in #forth ? 18:24:32 or just a new nick heh 18:24:34 --- nick: Blandest -> AlephNull 18:24:41 hi crow 18:25:02 aha hi alphe :) 18:25:13 is it tomorroe ? 18:25:13 ive got NO idea! 18:25:29 hey :> 18:25:47 My wife says the 18th is good 18:30:02 I got my ttyforth finished, the instruction stack being fed by the serial port, ill try to do a parallel port one, should be faster and easier to implement with less hardware 18:33:01 i printed the .lst and showed it to my class for an english semester work we had to do, nobody understood the assembly listing, but fortunately I got good grades lol 18:36:02 "this is an active channel" 18:42:14 alhpe when did chippie say that ? 18:42:39 i was quoting chanserv 18:49:07 aha 18:49:07 chanserv ? 18:50:06 the onjoin msg 18:53:43 aha 18:53:43 --- part: I440r left #forth 18:53:51 --- join: I440r (~mark4@1Cust185.tnt1.bloomington.in.da.uu.net) joined #forth 19:23:20 --- join: onetom_ (tom@adsl52014.vnet.hu) joined #forth 19:24:03 --- join: gforth0 (guest@adsl52014.vnet.hu) joined #forth 19:36:53 --- quit: AlephNull ("bye") 19:40:34 --- quit: onetom (Read error: 110 (Connection timed out)) 19:40:35 --- nick: onetom_ -> onetom 19:41:53 --- quit: gforth (Read error: 110 (Connection timed out)) 19:41:54 --- nick: gforth0 -> gforth 19:42:13 --- quit: Soap- (Read error: 104 (Connection reset by peer)) 19:45:16 --- join: Soap` (flop@210-55-151-166.dialup.xtra.co.nz) joined #forth 19:54:11 --- join: Herkamire (~jason@AC807637.ipt.aol.com) joined #forth 20:27:18 --- quit: CrowKiller (Read error: 32 (Broken pipe)) 20:28:45 --- quit: goshawk` (".") 20:32:06 --- quit: I440r (": sleep bed go tuck light off ; immediate") 20:49:25 --- join: goshawk` (goshawk@panix1.panix.com) joined #forth 21:53:43 --- join: onetom_ (tom@adsl52033.vnet.hu) joined #forth 21:54:03 --- join: gforth0 (guest@adsl52033.vnet.hu) joined #forth 21:54:16 howdy 22:10:53 --- quit: gforth (Read error: 110 (Connection timed out)) 22:10:53 --- nick: gforth0 -> gforth 22:12:11 --- quit: onetom (Read error: 110 (Connection timed out)) 22:12:12 --- nick: onetom_ -> onetom 22:19:28 --- quit: Soap` (Read error: 104 (Connection reset by peer)) 22:23:17 --- quit: Herkamire ("Off to more important things like sleeping or going outside or writing a forth") 22:39:52 --- join: Juk (ammu@baana-62-165-189-112.phnet.fi) joined #forth 22:47:17 --- nick: Juk -> juu 22:48:54 --- join: rob_ert (~robert@h237n2fls31o965.telia.com) joined #forth 23:01:26 --- nick: juu -> `Murr 23:03:21 --- nick: `Murr -> juu 23:11:03 --- nick: juu -> mur 23:59:59 --- log: ended forth/02.05.16