00:00:00 --- log: started forth/06.12.24 00:24:40 --- join: crest_ (n=crest@p548975A7.dip.t-dialin.net) joined #forth 00:36:29 --- quit: Crest (Read error: 110 (Connection timed out)) 00:47:33 --- join: Cheery (n=Cheery@a81-197-54-146.elisa-laajakaista.fi) joined #forth 01:33:17 this is a pretty cool post: http://groups.google.com/group/comp.lang.forth/msg/5291ef65ae56ad61 01:56:51 --- nick: crest_ -> Crest 02:32:45 starting unison 02:42:53 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #forth 03:47:44 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 04:10:50 --- quit: Crest ("Leaving") 05:33:57 --- join: zpg (n=user@81-178-111-22.dsl.pipex.com) joined #forth 05:52:29 --- quit: neceve (Remote closed the connection) 06:02:30 --- quit: zpg ("ERC Version 5.1.3 (IRC client for Emacs)") 06:18:41 hey 06:26:22 hi 06:26:56 what's up? 06:27:44 not much. 06:27:50 that is not good. 06:28:36 heh 06:52:20 --- join: nighty_ (n=nighty@sushi.rural-networks.com) joined #forth 06:55:15 --- join: Crest (n=crest@p54894892.dip.t-dialin.net) joined #forth 07:03:06 cheery, that's ok, everybody needs a break now and again :) 07:16:16 --- quit: virl ("Verlassend") 07:18:32 --- join: Crest|OS9 (n=Crest@p54894892.dip.t-dialin.net) joined #forth 07:20:55 --- quit: Crest|OS9 ("") 08:28:56 --- join: crc (n=crc@pool-70-110-140-19.phil.east.verizon.net) joined #forth 08:29:41 --- mode: ChanServ set +o crc 08:56:15 --- join: jackokring (n=jackokri@static-195-248-105-144.adsl.hotchilli.net) joined #forth 10:17:34 --- quit: crc (Remote closed the connection) 10:19:07 --- join: crc (n=crc@pool-70-110-140-19.phil.east.verizon.net) joined #forth 10:19:57 --- mode: ChanServ set +o crc 11:29:15 --- join: Al2O3 (n=Al2O3@pool-71-164-175-60.dllstx.fios.verizon.net) joined #forth 11:35:37 --- quit: Al2O3 ("Leaving") 11:43:19 --- join: zpg (n=user@85-210-169-84.dsl.pipex.com) joined #forth 11:50:31 --- quit: Baughn (Read error: 54 (Connection reset by peer)) 11:53:11 --- join: Baughn (n=svein@195134062077.customer.alfanett.no) joined #forth 11:53:42 hi Baughn 11:54:06 hi zpg. 11:54:40 hey Ray 11:54:56 Big plans for the holidays? 11:55:11 Hmm. linux-rc2-mm1-git crashed. I wonder why. 11:55:21 When's Boxing Day? Day after tommorow? 11:55:23 hi Baughn. 11:55:38 No plans, nope. Yourself? Yes, boxing day's Tuesday. 11:56:04 Small, intimate Christmas with my wife and kids. :) 11:56:29 Tho, they all have plans for later in the day, and I do not. 11:57:54 I'll prob'ly troll the chats, as usual. 11:58:14 :) 11:58:27 Good new! 11:58:31 news even 11:59:06 We've been accepted by the County to have a grant to complete the repairs we started on this house. 12:01:17 Over the years i've done about $16000 in work to the house. I lost a job a couple years back, and don't earn that kind of money anymore so... While i was out of work, Nan put in for the grant. It took two years but the inspector came out 3 days ago and approved $20000 in additional work, all provided by the County. 12:01:43 I nearly cried. 12:02:53 Congrats, sounds like great news. 12:07:05 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 12:07:15 The house is from the 1950's. A Frank Lloyd Wright experiment in single family starter homes. They could never have anticipated the electical needs of the 21's century. And being in Texas, the thing I'm most excited about is central heat and airconditioning. 12:09:48 use that thing FCKW? 12:10:48 Fox Chappel Killer Whales? 12:11:40 Flour-Chlor-Kohlenwasserstoffe? 12:12:40 the second 12:13:02 Checking into this... 12:13:49 Sounds like a refrigerant at first glance and taken in context. 12:15:35 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/") 12:21:29 --- quit: ygrek () 12:35:16 Scratching my head over fetching and storing 16 bit values in a clean way. 12:36:00 w@ and w! ? 12:36:10 undefined in ANS. 12:36:16 oh, okay. 12:36:27 fetching's not much of an issue. storing is a tad trickier. 12:36:28 intregal part of many colorforth words. 12:36:42 you have to swap the bytes? 12:37:15 AL becomes AH and visa versa? 12:37:29 I'm not on x86, dealing with the accumulator. 12:37:34 okay. 12:37:38 http://groups.google.co.uk/group/comp.lang.forth/browse_thread/thread/ae6b12537254784/34933e1f599f24ab?lnk=st&q=gforth+%2216+bit%22+store&rnum=1&hl=en#34933e1f599f24ab 12:37:44 i'll just port this i guess. a slight hassle. 12:40:18 as i thought. 12:40:39 the implementation you mean? or the hassle? 12:41:48 hehe. 12:43:32 on the x86 there is a machine instruction that swaps the Hi and lo order bits and in colorforth we make use of this instruction. fairly trivial. 12:44:13 * zpg nods 12:45:42 I've ported some basic functionality from a C programme, but it uses a 'short' (16bit) array -- of course, I can only get at 8-bit or 32-bit as it stands. This situation came as something of a shock. Insulation from the machine. 12:46:23 2 successive chars out of the question? 12:46:59 nope. 12:47:09 using "c@" is quite a clean approach. 12:48:12 i need to split the TOS into two 8-bits in order to use "c!" though 12:48:33 might be cleaner than Ertl's suggestion, at least it would rely on an existing abstraction. 12:49:26 Oh, sure, I get it now. 12:49:35 what's the struggle? Define w@ and w! for your Forth and note that they may require adjustment when porting. 12:49:36 forgot about the c!. 12:50:15 Quartus_: no struggle as such, just pondering the cleanest way to go about this. and yes, noting that they're not portable isn't a problem either. just me using it, and cross-machine it'll be 32-bit gforth all the way. 12:50:42 You know, zpg, I often have thoughts about the 'hassel' of some words, but those thoughts usually culminate in my wondering about my laziness. hehe :) 12:50:51 if speed matters, write them as tiny code words. 12:51:06 ... my laziness, which happens to be vast. :) 12:51:54 and... Hi Quartus :) 12:54:05 hey :) 12:54:46 yes, this seems pretty clean actually. 12:55:03 Big plans for the holiday, Quartus? 12:55:09 or did I already ask you? 12:55:39 you didn't. I'm visiting family; there now. How about you? 12:57:27 Families are entirely too far away to visit. :( Quiet, intimate celebration in the morning with Nan and kidlets, followed by her going to work and kids socializing... I find myself alone on another holiday and I'm thankful for the decompression time. 12:58:45 Now that our kids are older, Nan gives by relieving those at work with younger families. Besides, we can't sneeze at the income. 13:00:32 so much for a white xmas in canada 13:00:50 I can go outside wearing a tee shirt 13:00:56 hi nighty_. :) hope you are well. Plans? 13:01:10 Raystm2: Hi :) I am well and you ? 13:01:24 I am Wellbutrin. :0 13:01:25 :0 13:01:27 :) yikes 13:01:41 yes, it's one of those occasionally wam Decembers we get. 13:01:50 --- join: ttuttle (n=tom@gentoo/contributor/ttuttle) joined #forth 13:01:51 ya. temp? 13:01:56 Merry Christmas, etc... 13:02:07 still in the 20cels? 13:02:09 Raystm2: I think something like 12°C 13:02:11 springlike temperatures 13:02:17 or more 13:02:19 Merry Christmas ttuttle :) 13:02:30 hi ttuttle 13:02:36 Quartus_: Hi, how are you? 13:02:43 hi ttuttle 13:02:49 nighty_: hi 13:02:53 not bad thanks. You? 13:03:14 Quartus_: Good. I just got my Gentoo install migrated to a 64-bit architecture. 13:03:24 fun? 13:03:26 Quartus_: Yeah. 13:03:31 neat. 13:03:36 Good :) 13:03:45 Quartus_: Well it's pretty transparent to me, but I assume that double the registers and quadruple the register bits will make things run faster. 13:03:59 let's hope. 13:04:00 Quartus_: Plus I had a process the other day that allocated 1 TB of virtual memory. 13:04:21 Quartus_: (It only used the first page of each gig, though. I wrote it so I could see top show me a process with 1 TB of virtual memory used) 13:04:28 greed! 13:04:31 Quartus_: ;-) 13:04:44 Quartus_: /me only has 2 GB physical RAM + an almost-4 GB swap partition 13:04:44 ...run faster. Unless it's a windows machine where no matter what mechanical advantage the machine, it still runs as fast as programms in Windows 3.1. 13:04:59 Raystm2: lol windows 3.1 ftw! (everything since has been worse) 13:05:05 you have a tb of storage on that new laptop? :) 13:05:11 Quartus_: no 13:05:22 Quartus_: Notice I said it only used the first page of each 1 GB allocation. 13:05:36 Quartus_: Linux actually allocates memory when it is used, not when it is malloc'ed. 13:05:44 right. Doesn't allocate until use I presume. 13:05:53 Quartus_: It's a bug, from my point of view, since it has to kill some process when it runs out. 13:06:21 oddly I'd still expect an error if requests exceeded maximums. Perhaps I'm a traditionalist. :) 13:06:25 Quartus_: All the checks for malloc returning NULL don't really matter (well, it returns NULL if you allocate something ridiculous, but you can't actually [AFAIK] allocate more than 4 GB at once, since malloc takes a 32-bit int) 13:06:42 Quartus_: Yeah, I would to. It's configurable -- echo 0 > /proc/sys/vm/overcommit_memory; 13:06:54 ah ok. 13:07:06 s/to/too/; # eek 13:07:29 I haven't been elbows-deep in the kernel for awhile. 13:07:43 Quartus_: Nor have I. I've fixed a few little things here and there. 13:10:08 can you request >4gig with calloc? 13:10:19 Quartus_: Yes, but it tries to zero it before returning. 13:10:23 Quartus_: Which means I won't ever get it. 13:11:08 right. I was just considering the issue of malloc's parameter. 13:11:14 Quartus_: Yeah, I know. 13:11:32 Quartus_: Well on a 64-bit system, size_t *should* be 64-bit. I guess it's not. 13:12:07 I don't know. Would depend on the internal memory managment as some level. 13:12:23 *at 13:12:28 Hmm. sizeof(size_t) = 8 = 64 bits. 13:15:11 * ttuttle feels sheepish. 13:15:23 I wasn't using long arithmetic in multiplying 4 * 1024 * 1024 * 1024 so it overflowed. 13:15:24 heh 13:15:58 :) 13:16:11 I think I actually have it set up right. It will allocate me 5 GB, since I've got ~6 GB of virt mem, but it will return NULL for malloc of 32 GB, since I don't have anything near that much. 13:16:17 Quartus_: btw, where does the "w@" and "w!" convention come from? 13:16:24 now give it a go in gforth! :) 13:16:29 Quartus_: lol 13:16:39 zpg, ancient times. 13:16:49 w = word 13:16:54 zpg: Back when "wide" meant 8 bits instead of 4. 13:17:05 yikes 13:17:09 zpg: i was kidding 13:17:13 16 actually. 13:17:46 8088 days? or are we talking when Forth was but a blossoming idea.... (insert chimes here) 13:18:02 back in the day, byte was usually 8, word was usually 16. 13:18:10 Quartus_: gforth allocated 5 GB for me. 13:18:19 oh sorry, standard definition for a word. 13:18:26 in the late 70's through to the early 90's. 13:18:34 But Quartus_ but not 32 GB (it returned -524). 13:18:36 yeah, makes sense. just gets a little messy with redefinitions etc. 13:18:56 brb 13:19:02 ttuttle, sure. Gforth wraps malloc 13:19:23 Zpg, redefinitions? 13:19:59 I've seen word used as register width too. 13:20:07 hence 8086 word = 16bit, 80386 = 32bit etc. 13:20:19 oh. You mean the term itself. 13:20:23 yep. 13:21:07 it's 16 by common convention in Forth. On a 64-bit cell system you'd probably want one for 32 as well. 13:21:44 anyway, here's a brief anecdote: looked at some old C code, read quite well. thought, i'll port that to forth. did so, looked a little scared, it seemed totally arcane. then refactored for about 10-15 mins, and prefer the forth code by a mile. 13:22:07 neat! What does it do? 13:22:16 DSP / sine wave generation to 16-bit array. 13:22:34 My short bit of Forth code uses 32-bit cells at the moment. That aside, it works the same. Uses the FP stack. 13:22:35 You might could even generalize the rotation part of the word to take a count for all three -- c! w! dw! and the fetches... an idea. 13:22:58 Raystm2: by this convention, "dw!" is "!" 13:23:14 :) I suppose on a 32 bit system that's true. :) 13:23:27 ray, sure. Usually those map to single machine instructions, so the factoring isn't productive. 13:23:38 Cool. thanks Quartus. 13:23:45 Save a life... 13:23:53 heh 13:24:01 I dislike C a lot more than I used to, it seems. 13:24:05 Tainted :) 13:24:09 hehe. 13:24:24 c will look increasingly arcane as you practice with Forth. 13:24:24 You wonder why some of us say we've never gone back. 13:24:53 Not that i as anykind of c brain trust... 13:26:09 Well, obviously late-binding dynamically typed languages give one a different perspective. Forth is curious, it seems able to cleanly encompass low and high levels. Pointers in particular just look ugly as hell. Not to mention wanting to peek at values for debugging purposes. Where's that "dup ." I've been using?! 13:26:45 :) 13:27:42 * Raystm2 notes that duppa is butt in Polish and may Americans have the new 64 bit duppa's... 13:27:51 may = many even. 13:28:12 forth isn't dynamically typed, even. Even further afield. :) 13:32:08 ray. Heh 13:32:10 I've been wondering all the talk about GC and types. Are types truely necessary for GC ? 13:32:50 * Raystm2 born on the French side of a predominatly French/Polish New England Towne. 13:33:14 There're GC libraries for Forth. 13:33:27 Quartus_: of course, the typeless is very interesting indeed. 13:33:58 Not that i've needed GC yet, forbid that day that I build something that uses all of memory. A mild interest. 13:34:26 It would depend on what you mean by gc. 13:35:10 Seems to me that forth compiles so fast you could just make a few necessary copies of things on disk and warmboot to re-establish memory demands. 13:36:27 afaik there's nothing you can do with gc that you can't do without it. 13:36:51 Okay, I suppose that's where I was heading. 13:37:00 I thought as much. 13:38:21 you might speak with slava, though, as he's a gc proponent. 13:38:48 Hmm, it seems my "w@" and "w!" don't take signing into account. 13:39:05 I want to explore slava's GC. 13:39:21 did you rotate or shift? 13:40:09 using AND and shifting. 13:40:31 does rotate maintain sign on your machine? 13:40:37 you want the result sign-extended? 13:40:55 oh better question that. 13:41:31 well (address) -2 (address) w! w@ should print -2 13:42:15 it need not so do. Try that with c@ 13:43:18 well, the binary value is u. 11111110 ok 13:43:29 i'm definitely frying that with my word words 13:44:08 --- join: slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 13:44:08 --- mode: ChanServ set +o slava 13:44:22 i'm doing a $F AND on the lower 8bits, then a $F AND on the upper 8bits and shifting right by 8bits 13:44:27 erm 13:44:32 upper ==> $F0 AND 13:44:34 frying 13:44:42 as in, screwing up 13:45:09 f is only 4 bits 13:45:27 christ, sorry about this. the usual mistypings prevail. 13:45:52 "$FF AND" for lower, "$FF00 AND $100 /" for upper. 13:46:23 er... 13:46:37 this doesn't make much sense? 13:47:16 so what's your w@ look like? Source? 13:47:27 : w@ ( addr -- word ) 13:47:27 dup char+ c@ $FF * swap c@ or ; 13:47:49 endianness? 13:48:01 LOW HIGH 13:48:12 so 12 would be 13:48:13 12 0 13:48:34 A quick way is @ ffff and 13:49:31 c@ does not sign-extend. I recommend the same for w@. 13:51:18 "@ $ffff and" isn't equivalent to "dup char+ c@ $FF * swap c@ or" 13:52:47 I may have the endianness turned around. Perhaps ffff0000 16 rshift 13:53:15 alternately, 2 + @ ffff and 13:54:38 i see. 13:54:49 what do you mean by the sign-extend suggestion? 13:55:57 I mean if you fetch 255 with c@ it isn't sign-extended to -1 in the cell. It's considered an unsigned value. So, likewise should w@ behave. 13:56:40 brb 13:56:47 well, why should forth not be tainted? 13:58:50 it's older than C 13:59:26 I was referring to myself. 13:59:55 hi virl 14:00:31 Quartus_: that's true. 14:05:09 forth as we know it is just about the same age as C. 14:08:28 according to wikipedia it's 3 years older than C 14:09:17 --- quit: jackokring (Read error: 113 (No route to host)) 14:09:23 not in its modern form. 14:09:55 that was a 71-72 timeframe. 14:10:16 in some sense, forth is stuck in that timeframe 14:11:15 but C evolved a little bit. 14:11:32 in another sense, you can add most any subsequent language feature to a forth. 14:11:54 c saw more widespread use than forth, and it was used for harder problems. 14:12:44 forth also evolved. 14:13:20 look at the great advanced werty is making. :) 14:13:51 s/ed/es/ 14:14:41 Forth is somewhere stucked between toy applications and bigger applications. in fact it never has jumped to the second, or is today a webbrowser which is written in forth? 14:15:42 I'm sure werty can do it in 2 days. 14:19:14 I think that's depressing 14:21:13 c is a bell lab profit plot. forth is still pure of such nonsence, afaict. 14:21:44 yes, every time you write a line of C, bell labs profits. 14:22:00 and nobody, ever, has made any money from forth. Forth Inc is just a conspiracy 14:22:20 shh 14:22:59 sorry, i did say is, didn't i. meant was. 14:23:37 "Everytime when you write in C, so not in Forth, Bell Labs get's mone. Please think of the forthers" 14:23:47 hehe. 14:24:26 That was the 'Bill Clinton "is" '. 14:24:55 or "Everytime when you write in C a Forther dies. Please think of the Forthers" -> we need a sadly looking forther, perhaps Quartus? 14:25:36 aren't you the one who's constantly sad, depressed, and filled with hate? 14:25:51 I don't recall anybody holding busness hostage by training programmers in forth and ... you know the rest. 14:27:45 --- join: jackokring (n=jackokri@static-195-248-105-144.adsl.hotchilli.net) joined #forth 14:28:18 * Raystm2 goes back to learning how opcodes are formed. 14:28:51 x86 opcodes are nasty 14:29:03 keebler elves do it. 14:29:05 as i am learning, or, knew already.. 14:29:07 hehe. 14:29:29 keebler elves? they use love. keebler orcs I'd believe. 14:29:33 virl: the useful subset is not THAT bad 14:30:42 WAIT. Now that i'm diabetic, Keebler elves turn out to be evil so... Quartus, I agree now! 14:30:56 heh 14:33:17 yes, the small one-two byte subset isn't so bad 14:33:34 no, i mean the usual instructions like MOV, ADD, the basic SSE stuff 14:33:36 JMP, etc 14:33:46 I understand it's a might easier in octal. Opinions? 14:34:02 it is for x86 14:34:12 * Raystm2 remembers Cherry mentioning... 14:34:14 ya. 14:35:30 Motivation. I saw an opcode ( little endian ) 8b66 but did not find an instruction in the MASM raw opcode list of 66. I assume it's a construction. 14:36:37 Motivation continues... : w@ 8b66h 3, ; 14:38:22 regardless of its merits, we're stuck with x86 14:38:35 just like you may hate xml but sometimes one has to read or write xml to interoperate with other programs 14:40:54 luddite! 14:42:03 you are clearly not the World's Greatest Systems Programmer. 14:42:26 Why all this luddite bashing? Jacquard turns in grave when ever luddite is mentioned. 14:42:57 what's a luddite? who's a luddite? 14:43:05 is that a cult ? 14:43:08 yes. 14:43:12 well sorta. 14:43:24 werty werty werty 14:43:30 wert is here? 14:43:38 Specifically, Quartus is quoting werty... 14:43:42 oh 14:43:45 as I have learned. 14:43:50 I wanna talk to werty in irc 14:43:55 * Raystm2 has never read a werty. 14:44:31 http://en.wikipedia.org/wiki/Luddite 14:44:38 does werty really matter? 14:45:04 does anything really matter? 14:45:09 werty helps to centralize teh whole argument. 14:45:12 oh yes. 14:45:20 matter matters, apparently. 14:46:21 When you have a werty in the mix, everyone else that doesn't agree finds ways to gel. 14:47:49 werty, bah the name is so bound to an american keyboard. 14:47:54 instabond, out of fear :) 14:47:58 :) 14:48:14 I have defined quiop as the anit werty. 14:48:16 his europy name is zerty. 14:48:21 hehe. 14:48:43 anit/anti sorry. 14:48:47 ehm no.. 14:48:54 verty? 14:49:10 wertz would be the european name, if we use a german keyboard layout. 14:49:19 I see. 14:49:23 :) 14:49:54 quiop are the remaining letters in the first row, which must mean the totally opposite, therefore correct, point of view. 14:50:09 on german keyboard you can't type 'typewriter' in one key line like in the american layout 14:50:23 eh, english layout. 14:50:24 what, werty's not correct!!?! 14:50:54 This is what I've gleened from your conversations with slava, where I get all of my werty ref. 14:51:06 heretic! 14:51:14 the first row of my keyboard is: qwertzuiopü 14:51:19 I would not even be aware there was a werty for you both.. 14:51:35 neat. 14:52:32 resetter stweardesses 14:52:37 er, stewardesses 14:52:39 maybe his name is actually werty. 14:52:55 so the anti werty for them that buy Her Keyboard = quiopÜ 14:53:04 oops. :) 14:54:01 absentia: sorry PC = Flight Attendant. Please update. 14:55:47 you can't type flight attendant with only the left hand 14:56:07 ah, hell why is it so hard to write in gforth a code primitve? finding the stack layout could be made easier. 14:56:09 I think stewardesses is the longest english word that you can type using only keys meant for the left hand. 14:56:26 Yes you can. /me can use the entire keyboard with either hand from years of holding the phone and typeing orders. 14:56:32 someone said that gforth had tutorials somewhere? 14:56:43 you still haven't even looked? 14:56:51 you've been talking about learning forth for some far-fetched AI project for weeks now 14:56:53 I've looked around 14:57:01 how can you do AI if you can't find a tutorial? seriously 14:57:03 It's not included? 14:57:08 * Raystm2 finds this odd. 14:57:15 just found the manuual 14:57:16 it is included. 14:57:18 # info gforth 14:57:18 hehe .:) 14:57:19 is that what people are talking about 14:57:44 chapter three is "Forth Tutorial" 14:57:46 ah 14:57:46 k 14:57:51 --- quit: Crest ("Leaving") 14:57:57 "Forth Tutorial" is a tutorial pertaining to Forth, oddly. 14:58:04 Nut-uh. 14:58:14 wait, so it is. 14:58:20 Yeah, someone'll have to explain this crazy naming scheme to me. 14:59:14 Starting Forth doesnt' start your interpreter, and Programming Forth doesn't program anyting for you, and Thinking Forth... hell, let us not even go there. 14:59:28 :-) 14:59:48 --- join: Crest (n=crest@p54894892.dip.t-dialin.net) joined #forth 15:00:13 damnIT Crest missed my hillarious retort. 15:00:25 ? 15:00:38 okay okay Self-proclaimed hillarious... 15:01:03 damnIT Crest missed my hillarious retort. 15:01:10 Starting Forth doesnt' start your interpreter, and Programming Forth doesn't program anyting for you, and Thinking Forth... hell, let us not even go there. 15:02:22 *gg* 15:02:39 --- quit: ttuttle ("leaving") 15:03:27 whoa, 15:04:34 my wife claims that, on occasion mind you, I'm so engrossed with things that "don't matter" to quote slava, that I don't notice her. She just kissed me goodbye and it didn't register till the car left the driveway. 15:04:55 so engrossed as you were in quoting yourself :) 15:05:27 Not so much that as having re-read it several times to be sure I was proud of myself. whoa, now that's wellbutrin for ya. 15:07:43 It's all part of my learning disablility. I have to re-live moments over and over and over even. 15:09:55 You can easily notice people with this same disablility. They will tend to take a drink right after saying something, or mouth the words over again while someone else speaks. This gives the chance to re-weight the thought, which was heavily weighed before sent to begin with. 15:13:08 Wellbutrin means that I still do stuff like that, but I'm not so self-consious about such things. 15:13:09 --- quit: Baughn ("FS inconsistency, wish me luck") 15:14:58 well, ... Butrin! 15:15:39 Must be why I like to play music. I can practice a phrase over ad infinitem, or get the pleasure of going mindless all the way thru a piece. 15:18:54 --- quit: jackokring (Read error: 145 (Connection timed out)) 15:19:24 Such people can easily be considered self centered when infact they are in fear of what others think. Wellbutrin means not giving a sh*t what others think. 15:20:13 --- join: Shine (n=Frank_Bu@xdsl-84-44-227-168.netcologne.de) joined #forth 15:20:50 So, what do you think? 15:21:10 heh 15:21:12 I don't give a shit! 15:21:20 hahahahaha 15:25:17 I do claim these chats ( starting with #c4th-ot a couple years ago, and now #forth) have been the turn around in my recovery. I was in a bad way back then and am not sure where that road led. I say all ya'll saved me. 15:26:11 Thank you, each and every one. 15:26:34 hey, that's ok. Just don't read werty, you'll backslide. :) 15:27:08 :) 15:27:18 Well advised. 15:28:55 There was absolutely no-one in my world that could converse with me in a technical way till these chats. I like to claim that I only join chats where the IQ is atleast 10 points more then mine, but that was #c4th-ot. hehe. 15:36:27 :) 15:42:46 join/ ##psycotic-programmer-wannabe 15:43:40 yikes that should read ##werty. 15:44:07 heh 15:44:11 --- quit: Shine (Nick collision from services.) 15:44:15 --- join: Shine_ (n=Frank_Bu@xdsl-84-44-134-101.netcologne.de) joined #forth 15:44:30 --- nick: Shine_ -> Shine 15:44:40 Quartus: you're visiting just now? 15:44:55 I am. 15:44:59 you on the 'berry' then? 15:46:29 Well, I ended up adapting Ertl's 64-bit -> 32-bit code. Added "w." for signed printing. 15:46:41 * Raystm2 picks up twelve-string. 15:46:44 The signal processing stuff works fine with a 16-bit array. 15:46:45 requests? 15:46:51 oh hey cool. paste? 15:47:08 okay, it's a bit ugly though. 15:47:19 So am I and I still got married... 15:47:30 I don't know what that means. 15:48:09 * zpg chuckles 15:48:25 zpg. It will be impressive to someone like me until Quartus critiques and then I'll still have your side until I understand Quartus. 15:48:25 Yes who is werty 15:48:39 I always see some post of him in several newsgroups 15:48:47 nighty_ That's him. 15:48:49 especially forth 15:48:52 http://forth.pastebin.ca/291266 15:48:56 thanks zpg 15:49:25 sure 15:49:36 OH this is sig proc ya? 15:49:39 neat. 15:49:43 yeah, care to see the w@ stuff? 15:49:46 just what i'd like to see more of. 15:49:56 ya that's what i thought you'd post :) 15:50:46 http://forth.pastebin.ca/291268 15:51:02 hey this sorta looks like an oscilliscope. 15:51:19 what does? 15:51:35 that last paste? 15:52:37