00:00:00 --- log: started forth/18.10.11 00:03:14 --- quit: wa5qjh (Remote host closed the connection) 00:05:43 --- join: wa5qjh (~quassel@175.158.225.194) joined #forth 00:05:43 --- quit: wa5qjh (Changing host) 00:05:43 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 00:56:01 --- join: ncv (~neceve@2a02:c7d:c5c9:a900:6eaf:6ef7:3b81:d5f6) joined #forth 00:56:01 --- quit: ncv (Changing host) 00:56:01 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 00:58:08 --- quit: X-Scale (Read error: Connection reset by peer) 01:20:01 --- quit: lonjil (Ping timeout: 252 seconds) 01:23:01 --- join: lonjil (~quassel@2a02:418:6050:ed15:ed15:ed15:e741:32d6) joined #forth 01:56:34 --- join: gravicappa (~gravicapp@ppp83-237-167-197.pppoe.mtu-net.ru) joined #forth 02:04:13 --- quit: ashirase (Ping timeout: 246 seconds) 02:10:27 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:13:21 --- quit: pointfree[m] (Ping timeout: 276 seconds) 02:13:35 --- join: pointfree[m] (pointfreem@gateway/shell/matrix.org/x-nkrtuoghriefwpcv) joined #forth 02:16:18 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 02:19:14 --- join: rdrop-exit (~markwilli@112.201.162.180) joined #forth 02:26:02 Massive thanks yunfan 02:26:24 WilhelmVonWeiner: so you want to implmenmt a forth for that? 02:27:08 Maybe. I want to see what can be done with a USB device with a documented controller, first. 02:33:12 WilhelmVonWeiner: ok,. when you invented a forth for it, please allow me to have a try 02:34:31 I'll ping you in 20 years or so 02:35:17 :D 02:35:29 its just a mcs51 02:35:37 and sdcc had support it 02:47:42 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:02:40 --- quit: jedb (Ping timeout: 246 seconds) 03:26:25 --- join: jedb (~jedb@2604:6880:c742:5a70::f3e) joined #forth 03:48:34 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 03:57:24 --- quit: Zarutian (Ping timeout: 252 seconds) 03:59:48 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 04:03:22 --- join: siraben (~user@unaffiliated/siraben) joined #forth 04:05:32 MrMobius: Well, in your example that's 63356 which is = 0 because of 16-bit overflow 04:05:53 KipIngram: My implementation of HERE is it as a variable. 04:06:18 It seems to be correct. I think what's causing the crash is _running_ code outside of the current program memory is invalid. 04:07:18 I'm reminded of this quote: 04:07:19 "For reasons of security, the TI-83 Plus will crash if PC is ever $C000 or greater. This is a mega-bitch, because it means the executable part of a program can never exceed 8811 bytes." 04:07:47 http://tutorials.eeems.ca/ASMin28Days/lesson/day13.html#rel 04:08:57 This is a huge problem. I don't have enough storage after HERE (only 768 bytes). 04:10:53 Technically I get 768 more if I write to the address SaveSScreen (0x8265), but if the calculator powers down automatically I'm screwed. 04:11:18 ^PC being the program counter 04:16:58 I might be able to reduce program size more by defining more words in Forth instead of assembly, but at the expense of speed. 04:20:17 Ah, I'm considering this: since we can't execute a word when it's out of program memory, we can instead copy it entirely into a buffer and execute that. Since I'm direct-threaded, if that word contains addresses outside of program memory, then copy those words as well and execute. 04:20:30 i.e. a version of NEXT that can check for out of bounds PC 04:24:41 OR, I could avoid this entirely by not having a CALL DOCOL just after the link. 04:24:51 That's really the only executable part of words. 04:33:19 Oh, that would change the threading strategy. 04:33:47 --- quit: gravicappa (Ping timeout: 272 seconds) 04:42:38 Is your goal to have a full blown Forth (i.e. including outer interpreter) on the TI-83? 04:43:30 What do you mean by an outer interpreter? 04:43:41 Well, the nice thing about a threaded Forth is that the threaded definitions aren't code - technically they're data. 04:43:59 Indirect threading makes that a docol pointer. 04:44:10 Right, which means there's no making PC > $C000 or whatever it was that made it crash 04:44:18 Right. 04:44:35 The other nice thing about that, on a system with a separate instruction cache, is tha tyou can likely get your entire binary image into the cache. 04:44:53 So in the first short period after starting, it all gets cached in, and then from there on out just runs from there. 04:44:55 Sweet. 04:45:42 rdrop-exit: I already have the interpreter defined in Forth itself. So it is full-blown. 04:45:49 I'm just annoyed that I don't have more space to work with. 04:50:30 Only your primitives need to fit below $c000, sounds like plenty of space, how much of that $c000 is reserved by the TI’s own code? 04:51:01 rdrop-exit: He's direct threading, so there's a snip of code before each definition. 04:51:03 I think, at least. 04:51:25 Aha 04:51:39 Sounds like an ideal environment for indirect. 04:53:17 Indeed, indirect or token. 04:54:46 rdrop-exit: I shouldn't overwrite RAM outside my program. I ask the OS to allocate 1024 bytes for a "program", basically giving me free space. 04:55:04 And lo and behold the address of the allocation exceeds $c000 04:55:11 KipIngram: Right. Indirect it is. 04:55:23 Shouldn't be too hard, since it affects WORD words the most. 05:02:01 Yeah, I don't think it'll take you long to switch it over. 05:03:50 Also, just FYI, occasionally you run into a processor on which indirect threading is FASTER. Maybe you'll be that fortunate. 05:04:20 Depends a lot on the effecitiveness of the processor's subroutine call/return features. 05:04:26 effectiveness 05:04:53 Oof, looks like I'll lose BC as a TOS 05:05:06 Uh oh. Just short on registers? 05:05:17 That sucks. 05:05:19 Changing DOCOL also requires changing NEXT, right? 05:05:31 Yes, they both have to change. 05:05:48 And yeah, usually indirect threading winds up needing an extra scratch register. 05:06:01 That one is usuall referred to as W. 05:06:21 BC = TOS, IX = RSP, HL = W, DE = IP, SP = PSP 05:06:28 With direct-threaded 05:06:32 Indirect threading next is basically w=*(ip++); jmp *(w++); 05:06:44 That leaves W pointing at the parameter field. 05:06:45 Looks simple with C code. 05:07:13 I'm short on registers. 05:07:39 What is the W item you have in HL? 05:07:50 It's not serving this purpose? 05:07:51 W is the working register, assigned to HL 05:07:55 a 16 bit register 05:08:04 They're all 16 bit anyway 05:08:32 So once you've finished NEXT and gotten into a primitive, it's free to use W for whatever - you don't need it anymore. 05:08:57 If I were to not make BC a TOS, that would be bad because it would require huge code changes 05:09:02 Every single CODE word goes. 05:09:03 docol, dovar, etc. use it, to get at the parameter field, but primitives rarely use it for anything. 05:09:11 Yes. 05:09:23 But does your W have to be preserved across words? 05:09:50 Nope. NEXT overwrites it 05:10:09 With the address of the pointer to the destination 05:10:09 Ok. I'm not clicking, then, to why you're needing a new registers for the change. 05:11:07 http://www.bradrodriguez.com/papers/moving2.htm 05:11:16 Scroll to the Z80 for the listings for DTC and ITC 05:11:45 If you can find a copy of the following book, the first chapter has the best discussion and comparison of the different threading types I’ve seen, along with x86 code samples for each. https://mitpress.mit.edu/books/interpretation-and-instruction-path-coprocessing 05:13:08 Correction, it’s the second chapter. 05:13:35 Be right back. 05:21:28 --- quit: wa5qjh (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 05:24:05 Ok. Let me take a stab at indirect. 06:16:15 --- join: TCZ (~Johnny@ip-91.246.66.247.skyware.pl) joined #forth 06:44:07 Err. It's still problematic. 06:44:46 I'm trying to do this: [ Link pointer ] [ length + flags ] [ NAME ] [ addr of DOCOL ] .... [ addr of EXIT ] 06:46:39 --- quit: TCZ (Quit: Leaving) 06:50:26 --- quit: ncv (Remote host closed the connection) 06:50:44 --- join: ncv (~neceve@86.127.177.21) joined #forth 06:50:44 --- quit: ncv (Changing host) 06:50:44 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 07:12:28 --- quit: dave9 (Quit: dave's not here) 07:13:32 It's just not "working"? 07:13:51 You don't put addr of exit at the end; you put the CFA of the EXIT word. 07:14:00 And THAT points to EXIT machine code. 07:14:14 I.e. EXIT I call it (;)) is a primitive. 07:14:30 Maybe that's what you meant? 07:15:43 Ooops, missed my opening (. 07:15:50 (;) is my name for the EXIT primitive. 07:17:34 But I assume [addr of DOCOL] is a pointer to the docol *code*, so if your nomenclature is consistent the [addr of EXIT] would be a pointer to code as well. 07:17:39 The thing is a CALL (ADDR) instruction takes 3 bytes on the Z80 07:17:45 Maybe I'm depending on that 3 bytes somewhere 07:18:02 Could be. You should wind up needing only JUMPs here. 07:18:32 But at the end of each definition you have a cell that points to a pointer to EXIT, just like, say, + would be a cell that points to a pointer to the + code. 07:19:53 Ok what I should do is write a minimal core 07:20:01 Just enough for debugging 07:21:21 Well, what about my comment? The last pointer in each of your definitions - does it point to code or to a code pointer? 07:24:05 --- quit: rdrop-exit (Quit: rdrop-exit) 07:25:03 Points to the start of the CFA for that word 07:25:17 i.e. EXIT points to the first instruction following the header 07:25:39 And that spot points to the actual code? 07:29:39 Right. 07:30:15 Ok. So my minimal Forth is working, I'll add a base interpreter. 07:49:36 --- quit: tabemann (Ping timeout: 250 seconds) 08:05:47 how is it, does TI-83 have an serial port? usually they look like minijack or microjack (which is even smaller) 08:23:41 I use the actual device for a REPL. 08:23:58 I read input from the keypad and display it on the screen. 08:24:07 There's a USB cable for the computer to the TI. 08:24:31 Maybe I'll be able to figure out how it works and get a terminal on the computer to connect to the calculator. 08:24:34 Right now it's just flash and test. 08:24:50 Zarutian: It's the TI-84+, specifically. 08:40:19 --- quit: Keshl (Remote host closed the connection) 08:42:39 --- join: Keshl (~Purple@24.115.185.149.res-cmts.gld.ptd.net) joined #forth 08:45:46 --- join: ncv_ (~neceve@90.194.40.93) joined #forth 08:45:55 --- quit: ncv_ (Changing host) 08:45:55 --- join: ncv_ (~neceve@unaffiliated/neceve) joined #forth 08:48:07 --- quit: ncv (Ping timeout: 246 seconds) 09:27:49 --- quit: jedb (Ping timeout: 252 seconds) 09:29:24 --- quit: pointfree (Excess Flood) 09:30:01 --- join: pointfree (sid204397@gateway/web/irccloud.com/x-ceublzqobhaavqlu) joined #forth 09:31:00 --- quit: KipIngram (Ping timeout: 252 seconds) 09:32:27 --- join: jedb (~jedb@199.66.90.113) joined #forth 09:35:55 --- join: [1]MrMobius (~default@c-73-134-82-217.hsd1.va.comcast.net) joined #forth 09:35:58 --- join: KipIngram (~kipingram@185.149.90.58) joined #forth 09:36:22 --- nick: KipIngram -> Guest58255 09:38:19 --- quit: MrMobius (Ping timeout: 245 seconds) 09:38:20 --- nick: [1]MrMobius -> MrMobius 09:46:48 how often do you guys inline successive definitions 09:47:06 like : foo ... ; : bar ... ; : baz ... ; all one line 09:47:15 (sorry, I know "inline" usually means something else in this context) 09:48:58 I don't think it matters. 09:49:01 It's syntactic. 09:49:13 ^it definitely does not matter* 09:49:46 if it were c, I would generally frown on that - the rule of thumb is to separate different operations with a line break so that nothing gets hidden in the noise. but I always struggled with groking good, consistent formatting rules in functional languages, and now with forth 09:49:59 AFAIK it's not good style anyways. You should always start a new paragraph or line per word defined. 09:50:00 it seems common practice to be a lot more free-form 09:50:15 Ah, with Forth it depends. 09:50:21 You can do whatever you like. 09:50:33 But I tend to follow "convention", whatever that means. 09:50:49 At _least_ with naming my words. 09:50:56 And their semantics. 09:51:12 zy]x[yz: The C compiler (or equivalent) ignores a lot of formatting anyway. 09:51:22 I know, I'm asking about style 09:51:30 zy]x[yz: Which functional languages are you referring to? 09:51:51 Scheme/Common Lisp/Emacs Lisp have pretty solid conventions IMO 09:52:04 Haskell, maybe. I haven't read enough Haskell code to be able to tell 09:52:23 haskell and ocaml, but I really don't have a lot of experience with either of those. But it was a thing I remember from going through the hello-worlds and such - wondering how the heck to consistently format it 09:52:35 What editor are you using? 09:52:37 vim 09:52:39 Usually it boils down to that. 09:52:42 Oh. 09:52:47 Maybe get some packages to help with formatting? 09:52:49 I use Eamcs. 09:52:52 Emacs* 09:53:14 (let's not get into a holy war :) 09:53:17 well with forth, I use my own dialect, so I've rolled my own syntax file 09:53:36 I've never used emacs, so I don't have much of a dog in that fight 09:53:38 Ah, I should do that as well. There are some subtleties that annoy me only slightly. 09:53:51 I've used both. They're good for different reasons. 09:55:07 Bye for now. I have to go sleep. 09:55:34 --- quit: ncv_ (Remote host closed the connection) 10:04:08 --- join: X-Scale (~ARM@43.212.137.78.rev.vodafone.pt) joined #forth 10:07:01 --- nick: Guest58255 -> KipIngram 10:07:09 --- mode: ChanServ set +v KipIngram 10:08:06 --- quit: epony (Quit: QUIT) 10:08:23 I've used them both, and I also don't have much of a dog in that fight. 10:08:27 They're both quite good. 10:08:44 I think emacs may have a slight edge on "efficiency of motion." 10:08:47 But not much. 10:10:48 don't you end up using the arrow keys a bunch with it? 10:10:52 (and here goes the holy war) 10:11:07 --- quit: pointfree (Excess Flood) 10:11:44 --- join: pointfree (sid204397@gateway/web/irccloud.com/x-tvzqpunxfraienne) joined #forth 10:11:49 No, I swapped capslock and ctrl, and ctrl-letter keys are super easy. 10:11:59 I actually swap those keys for everything - vim too. 10:12:06 I *hate* the arrow keys. 10:12:37 That's why I give emacs a slight edge - you can activate those letter keys without having to "change modes." 10:12:43 Well, I guess you change modes when you push ctrl. 10:12:59 But it's not as "overt" as vim's esc/i "stronger" mode switch. 10:13:12 the only ctrl-keys I'm familiar with are ^A, ^E, and ^W 10:13:27 I use the arrow keys a lot in vim, when it's faster to do that than to escape to control mode, use the letter keys, and hit i to get back to insert mode. 10:13:56 I'm emulating the emacs style in my Forth. 10:14:01 yeah I see a lot of people around here using vim and reverting to arrow keys 10:14:05 it's painful to watch 10:14:05 ctrl-letter for line and command history navigation. 10:14:39 I use ctrl-[ for esc so my hands never move far from home row 10:14:45 Specifically letters that are RIGHT UNDER my right-hand fingers, since the left hand is hitting ctrl. 10:14:56 Ah, that's kind of a nice idea. 10:15:05 I'd never thought of that - that will help. 10:15:14 I really started doing it because my left wrist started hurting from hitting esc 10:15:26 also I often use ctrl-I instead of tab 10:15:40 I do that one too. 10:15:50 But wow - ctrl-[ is going to make me like vim even better. 10:15:53 Thanks. 10:15:57 np! 10:16:06 I knew that was code 27, but it just never occurred to me to use it in vim. :-( 10:16:17 Or to see if it worked. 10:16:24 yeah I don't know how it occurred to me. too me several years 10:16:40 Twisting my pinkie around to hit the ctrl key was what made my wrist sore. 10:17:00 Not to mention that they couldn't decide over the years where to put it. 10:17:09 That's not so bad anymore, but for a while it kept moving around. 10:17:14 I guess my idle position is with my left-hand kind down and to the left so my pinky is already there 10:17:25 maybe from a childhood of playing first person shooters 10:18:15 and yeah when keyboards put ctrl in the wrong place it's really annoying 10:18:45 a lot of laptops like to squeeze in a function key in there, and they can't agree on which key goes on the outside 10:18:55 so that's always frustrating when moving to a new laptop 10:22:54 Right. 10:23:00 But capslock is always in the same place. 10:23:18 And good grief - I could count on one hand the number of times I've used capslock function in the last decade. 10:23:28 But they give it that huge, valuably placed key. 10:23:49 I mean, it's ENORMOUS. 10:24:18 But that's perfect, in both ways, for ctrl. 10:24:41 I guess most people, though, don't really use the keyboard except for typing text. 10:24:51 typing 10:25:00 Oh, it was right the first time. 10:25:08 I misread it - thought I'd inserted an e. :-) 10:27:11 yeah that is kind of a stupid key to be so big 10:27:46 it should be up there with numlock and shit 10:28:05 --- quit: pointfree (Excess Flood) 10:28:42 --- join: pointfree (sid204397@gateway/web/irccloud.com/x-hrzwkzuvtxqmtxye) joined #forth 10:29:03 Yes, totally should be with the other lock keys. 10:29:15 I use laptops, so I don't have a number pad, numlock, scroll lock, etc. 10:30:09 I want to write a numerical work program with my Forth - I will probably define a "number pad" under my right hand (letter and punctuation keys), so that I can use it more like a calculator. 10:30:20 Numbers are not particularly easy to type off of the number row. 10:30:26 At least not fluidly and fast. 10:31:34 Maybe jkl = 123, uio = 456, 7890 = 7890. 10:31:43 Or maybe make m = 0. 10:32:01 +, -, *, / are all easy enough to get to. 10:32:43 sqrt is left hand, and sin and cos and so on would be "detectable." 10:32:50 They both have left hand first letters. 10:32:57 and so does tan. 10:33:45 Actually I just thought of that idea, so it's probably not very well-formed yet. 10:34:54 I used to have a laptop that had a numpad superimposed on the keyboard 10:35:05 I think numlock would enable it 10:35:40 I've seen those. 10:35:42 so it had like 123 on "nm," or something, and 456 on "jkl", and so forth 10:36:10 Right, I first thought that, but then I moved it up a row, because 789 are actually right there. 10:36:22 jkl, uio, 789 10:36:24 oh yeah, that's cool 10:36:53 I probably don't want this to be a total "mode" - I just want a fast way to activate it for entering numbers. 10:37:00 Forth syntax is already pretty good for calculating. 10:37:29 Maybe my option key (left hand). 10:37:43 I'll have to see what possibilities MacOS gives me in the termios mode I'm using. 10:38:07 Option is sort of like the real ctrl key, though - down there in an awkward place. 10:38:39 Nothing on the bottom row is very easy except space. 10:39:19 Anyway, this sort of thing is a big deal to me. I do 80-90 percent of my work in console windows, and I care a lot about it being "effective." 10:39:54 "Oh, wow - there are volume control keys up there... Fancy that." 10:40:07 WHO CARES???? You put control in the wrong place... 10:40:41 One thing I don't like about the Mac keyboard is having a power "key." 10:40:49 It's right up there above backspace (which they call delete). 10:41:02 sometimes I miss the backspace and hit the power key, and it sleeps my computer. 10:41:25 Would a REAL power switch have been that hard? 10:41:44 Common in gadgets these days, though - often you can't REALLY be sure the thing is off. 10:41:55 I want a SWITCH between the battery and the circuitry. 10:42:30 The whole spectre of the NSA listening to me even when my phone is "turned off"... Ugh. 10:43:11 heh, if that bothers you I have bad news 10:44:06 * KipIngram braces himself... 10:44:50 These people that say "if you're not doing anything wrong it shouldn't bother you" drive me nuts. 10:45:02 I'm NOT, and it DOES. Don't tell me how I feel about things. 10:45:27 I mean, you're always surrounded by electronics that could be listening, even if you take the battery out of your laptop. you should be building yourself a faraday cage 10:45:28 And yes, John Locke was my favorite character on Lost. 10:45:37 "Don't tell me what I can't do..." 10:45:46 Yeah, very true. 10:46:07 Our TVs, our bluray players, etc. Anything connected. 10:46:14 oh yeah, not that I think it should happen. but even if it's not the nsa, it's the chinese or something 10:46:45 My wife bought an Alexa a few months ago. I wasn't exactly thrilled, but it is her house too. I'm not her dad. 10:46:52 the chinese got caught a few months back stealing photos from consumer quadcopters 10:47:06 they had software in there sending everything it recorded back home 10:47:36 Yeah. 10:47:51 And also recently for spying on corporations through their Chinese built servers. 10:48:04 ah, didn't hear about that one 10:48:09 Seriously, guys, what did you expect? They are our ADVERSARIES. 10:48:12 At least in some ways. 10:49:40 at least with the nsa we can pretend to be outraged and have congressional hearings where they grill scapegoats and then nothing happens but everybody feels better 10:51:16 Yep. :-) 10:51:21 Siri is more fun than Alexa. 10:51:42 You ask Alexa about Hal, and she says "Hmmm, I don't know that one," or gives you a factural "fictional character account." 10:51:57 Siri pauses, and in an uncomfortable voice says "We don't like to talk about that..." 10:52:05 haha 10:52:11 There clearly are people at Apple trying to make Siri FUN. 10:53:40 "Alexa. Can I call you Siri?" 10:53:45 "That's not a name I can respond to." 10:53:49 How blah is that? 10:54:30 "Alexa. Will you be my girlfriend?" 10:54:35 "I like you, as a friend." 10:54:50 SHIT. Real women have told me that my whole life - do I have to get it from the virtual females too???? 10:56:12 well to be fair I'd be weirded out if my cat wanted to be more than just friends, and I think she has more self-awareness than alexa 10:56:43 :-) 10:56:53 I'm quite sure of it (the self-awareness). 10:57:18 That class of animals clearly knows what's up. 10:58:26 and even she has an electronic tracking device in her! you just can't escape it 12:05:09 --- join: tabemann (~tabemann@cpe-24-209-155-210.wi.res.rr.com) joined #forth 12:22:41 Real women don't have any stack operators 12:23:08 A stack will never break your heart 12:23:20 unless you break its' interpreter 12:27:52 --- quit: tabemann (Ping timeout: 252 seconds) 12:39:55 --- quit: ashirase (Ping timeout: 252 seconds) 12:42:47 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 12:51:23 --- quit: ashirase (Ping timeout: 246 seconds) 12:52:19 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 13:22:53 --- quit: dave0 (Ping timeout: 246 seconds) 14:48:46 --- join: dys (~dys@2a01:598:b001:93db:226:5eff:fee9:68d2) joined #forth 15:03:16 --- join: wa5qjh (~quassel@175.158.225.194) joined #forth 15:03:16 --- quit: wa5qjh (Changing host) 15:03:16 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 16:09:41 --- nick: bb010g[m] -> bb010g 16:18:43 --- quit: vxe_ (Ping timeout: 272 seconds) 16:23:26 --- join: epony (~epony@unaffiliated/epony) joined #forth 16:44:47 --- quit: siraben (Ping timeout: 250 seconds) 16:56:10 --- quit: nighty- (Quit: Disappears in a puff of smoke) 16:57:21 --- join: vxe (~vxe@31.153.239.35.bc.googleusercontent.com) joined #forth 17:53:24 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 18:05:32 --- join: tabemann (~tabemann@111-87-181-166.mobile.uscc.net) joined #forth 19:09:10 --- quit: dddddd (Remote host closed the connection) 20:03:46 --- quit: tabemann (Ping timeout: 252 seconds) 20:25:47 --- join: tabemann (~tabemann@162-225-198-161.lightspeed.milwwi.sbcglobal.net) joined #forth 20:45:29 --- quit: wa5qjh (Ping timeout: 268 seconds) 20:49:06 --- quit: tabemann (Ping timeout: 252 seconds) 20:53:36 --- join: wa5qjh (~quassel@175.158.225.208) joined #forth 20:53:36 --- quit: wa5qjh (Changing host) 20:53:36 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 21:05:55 --- join: tabemann (~tabemann@2602:30a:c0d3:1890:b90b:3bee:a83b:ed44) joined #forth 21:10:19 --- quit: sigjuice (Ping timeout: 252 seconds) 21:12:18 --- join: sigjuice (~sigjuice@107.170.193.86) joined #forth 21:29:22 --- quit: ecraven (Ping timeout: 244 seconds) 21:29:37 --- join: ecraven (~ecraven@www.nexoid.at) joined #forth 22:02:04 --- quit: dys (Ping timeout: 252 seconds) 22:18:11 --- join: dave0 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 22:26:48 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 22:27:24 hi 22:59:59 --- quit: wa5qjh (Remote host closed the connection) 23:01:52 --- join: wa5qjh (~quassel@175.158.225.208) joined #forth 23:01:52 --- quit: wa5qjh (Changing host) 23:01:52 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 23:59:59 --- log: ended forth/18.10.11