00:00:00 --- log: started forth/09.12.09 00:14:24 --- quit: PoppaVic (farmer.freenode.net irc.freenode.net) 00:14:24 --- quit: mathrick (farmer.freenode.net irc.freenode.net) 00:14:24 --- quit: proteusguy_ (farmer.freenode.net irc.freenode.net) 00:14:24 --- quit: tathi (farmer.freenode.net irc.freenode.net) 00:14:24 --- quit: kar8nga (farmer.freenode.net irc.freenode.net) 00:14:26 --- quit: Snoopy_1611 (farmer.freenode.net irc.freenode.net) 00:14:27 --- quit: nighty_ (farmer.freenode.net irc.freenode.net) 00:14:27 --- quit: TreyB (farmer.freenode.net irc.freenode.net) 00:14:27 --- quit: KipIngram (farmer.freenode.net irc.freenode.net) 00:14:27 --- quit: madwork (farmer.freenode.net irc.freenode.net) 00:14:27 --- quit: madgarden (farmer.freenode.net irc.freenode.net) 00:14:28 --- quit: hiredman (farmer.freenode.net irc.freenode.net) 00:14:28 --- quit: gnomon (farmer.freenode.net irc.freenode.net) 00:14:28 --- quit: yiyus (farmer.freenode.net irc.freenode.net) 00:14:28 --- quit: maht (farmer.freenode.net irc.freenode.net) 00:17:01 --- join: madwork (n=madgarde@204.138.110.15) joined #forth 00:17:01 --- join: KipIngram (n=kip@173-11-138-177-houston.txt.hfc.comcastbusiness.net) joined #forth 00:17:01 --- join: madgarden (n=madgarde@CPE001d7e527f89-CM00159a65a870.cpe.net.cable.rogers.com) joined #forth 00:17:01 --- join: nighty_ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #forth 00:17:01 --- join: TreyB (n=trey@76.254.113.201) joined #forth 00:17:01 --- join: Snoopy_1611 (i=Snoopy_1@dslb-088-068-206-113.pools.arcor-ip.net) joined #forth 00:17:01 --- join: PoppaVic (n=pops@adsl-99-150-133-146.dsl.sfldmi.sbcglobal.net) joined #forth 00:17:01 --- join: mathrick (n=mathrick@dlink214.imada.sdu.dk) joined #forth 00:17:01 --- join: proteusguy_ (n=proteusg@zeppelin.proteus-tech.com) joined #forth 00:17:01 --- join: tathi (n=josh@dsl-216-227-91-166.fairpoint.net) joined #forth 00:17:01 --- join: kar8nga (n=kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 00:18:01 --- join: hiredman (n=rattus@67.152.53.125) joined #forth 00:18:01 --- join: maht (n=maht__@85.189.31.174.proweb.managedbroadband.co.uk) joined #forth 00:18:01 --- join: yiyus (i=12427124@je.je.je) joined #forth 00:18:01 --- join: gnomon (n=gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 00:25:37 --- join: noelhenson (n=noel@75-106-241-179.cust.wildblue.net) joined #forth 00:44:21 hi. 01:01:29 --- quit: DrunkTomato () 01:06:55 --- join: ASau (n=user@83.69.227.32) joined #forth 01:09:52 --- quit: I440r (Read error: 131 (Connection reset by peer)) 01:18:58 --- quit: _dinya__ (Read error: 104 (Connection reset by peer)) 01:21:32 --- quit: ASau`` (farmer.freenode.net irc.freenode.net) 01:21:32 --- quit: schme (farmer.freenode.net irc.freenode.net) 01:22:23 --- quit: segher (Remote closed the connection) 01:25:07 --- join: segher (n=segher@84-105-60-153.cable.quicknet.nl) joined #forth 01:25:22 --- quit: segher (Remote closed the connection) 01:26:08 --- join: segher (n=segher@84-105-60-153.cable.quicknet.nl) joined #forth 01:51:45 --- join: Maki (n=Maki@dynamic-109-121-73-52.adsl.eunet.rs) joined #forth 01:55:34 --- join: schme (n=marcus@sxemacs/devel/schme) joined #forth 01:55:34 --- join: ASau`` (n=user@83.69.227.32) joined #forth 02:35:48 --- join: alex4nder (n=user@wsip-72-215-164-129.sb.sd.cox.net) joined #forth 02:35:50 hey 02:37:25 ho 02:41:02 --- quit: ASau (Read error: 104 (Connection reset by peer)) 02:44:50 ha 02:44:53 hello 02:45:44 Hey 02:46:43 now, come on.. Yer supposed to hit all the variants ;-) 02:47:44 --- join: ASau (n=user@83.69.227.32) joined #forth 02:50:03 ola 02:50:11 Que Tal 02:50:13 shalom 02:50:34 there yah go - got the spirit of it now! ;-) 02:50:53 I'm a slow learner 02:53:31 --- join: alex4nde` (n=user@wsip-72-215-164-129.sb.sd.cox.net) joined #forth 02:53:36 bounce. 02:53:53 The list is long. 02:54:05 http://hubpages.com/hub/How-to-say-Hello-in-100-languages 02:56:25 I'm suffering from architectural block. 02:56:57 alex4nderI've not heard that one before 02:57:10 brainfart? 02:57:26 mindmelt? 02:57:29 noelhenson: I've got a problem, and I can think of 3 or 4 solutions, but they all feel wrong. 02:57:36 yep 02:57:53 alex4nde`: walk around the problem, is my suggestion. 02:58:06 yah, that's good advice. 02:58:08 step back from it a level, even 02:58:15 but I've been walking around it 3 or 4 days. 02:58:23 gotta' love that 02:58:28 and I think the problem is that I don't have enough information to solve the problem. 02:58:43 so I've just got to make a choice, in order to move forward, and gather that information. 02:58:59 Can you iteratively decompose the problem to isolate what you do know from what you don't? 02:59:00 that could be true - or yer trying to solve 2+, or the *wrong* prob 02:59:35 noelhenson: in some ways, but there's an interesting overlap that I don't understand yet. 03:00:15 Tell us about the problem - maybe someone will see something new. 03:00:18 you've got requests for data coming into the system,.. that data is either available, or another request has to be made to gather the data for the first request. 03:00:57 4lex4nder: When that happens to me, I usually just start with the device drivers. It gives me time to think about the larger problem. 03:01:20 so the first request is queued, the request is made, and the data gathered or not 03:01:40 if the data isn't available in time, we throw out the request, and don't respond. 03:01:54 noelhenson: yeah, the API-ideas 03:01:57 (this is defined in the standard I'm implementing) 03:02:00 Is this a distributed system of peers? 03:02:18 With all of them holding some of the information? 03:02:25 KipIngram: it's a 'universal' translator for a set of protocols. 03:02:35 some protocols are broadcasting, others need to be requested. 03:03:00 so most complex case, I get a request for a protocol that needs to be requested 03:03:09 If the system you're referring to can't satisfy the request and has to issue more requests, to whom does it issue them? 03:03:10 simplest case, I rebroadcast what was just broadcasted to me. 03:03:38 KipIngram: another device, using whichever protocol that other device speaks. 03:04:09 And that other device, can it be considered equivalent to the "first" device, and it's running this same algorithm as well? 03:04:31 it could be the same, it could be totally different. 03:05:09 inetd on mescaline 03:05:12 And is timeout the only way to fail a request, or could the requestee respond negatively? 03:05:23 alex4nder: It sounds like keeping an in-memory copy of the data to be transferred might be a good approach. Broadcast and requested data would fill the table. Other threads would/could rebroadcast that data over the other channel(s). 03:05:42 KipIngram: depending on the protocol we're speaking when we get a request, it could be either way. 03:05:51 noelhenson: yah, that's where I'm leaning. 03:05:58 alex4nder: requested data could be handled in the same with with an additional thread that fulfills the requests. 03:06:02 Ok. If anything sparks I'll let you know. 03:06:09 noelhenson: with some type of notification to the threads when the data has been made available in the table. 03:06:10 You're writing this in Forth? 03:06:14 KipIngram: yup 03:06:24 Groovy. 03:06:37 --- quit: alex4nder (Read error: 110 (Connection timed out)) 03:07:11 alex4nder: The update information for rebroadcast could simply be a flag field associated with each data item. 03:07:45 alex4nder: Basically you would normalize all types of traffic through an in-memory buffer. 03:08:22 noelhenson: right, that's another issue, what is the data normalized to. because each protocol will want its own conversion. 03:08:27 well, I was thinking queue/circular-queue.. Don't mind me. 03:09:32 noelhenson: these units are all sensors on a network, and they have their own opinion on how data should be stored. 03:09:44 ahhh 03:10:04 well, their clients are supposed to normalize for the "server" 03:10:24 this is a translator box, it has to take all comers. 03:10:32 alex4nder: The normalization would depend upon the data. But without that information, I'd consider the idea of using ring buffers. But I'd have to think about that some more. 03:11:59 --- join: GeDaMo (n=gedamo@dyn-62-56-89-110.dslaccess.co.uk) joined #forth 03:12:22 alex (may I call you that?): But... this thought occurs: you might be better off treating your system as if it were something like an old-style telephone system. An operator task would take incoming messages (and/or message requests) and then route them to the appropriate output. 03:12:42 yup 03:12:49 usocks are yer friend ;-) 03:14:06 noelhenson: yup,. that's the visual I have. The issue in this case is that the operator needs to speak 5 or 6 different languages, and deal with the particular phone habits of the speaker he's talking to. 03:14:31 so what language does the operator take messages in? Does he translate it to english all the time for his own personal use. 03:14:32 umm.. Why? 03:14:47 it's a dispatcher. 03:15:27 --- join: scj (i=syljo361@static-ip-62-75-255-125.inaddr.server4you.de) joined #forth 03:15:33 Seems like there needs to be just enough common language to manage the flow. Like envelopes. What's inside doesn't matter until it gets to the final recipient. 03:15:43 alex: so, if I understand you, for each interface, there are not only several devices to be handled but there are several protocols for each interface. 03:15:44 PoppaVic: it is a translator, and it has to deal with the particular styles of communication. 03:15:53 noelhenson: there could be, yes. 03:16:00 Right: packet arrives, you chuck it into the apropos letterbox and wait for more packets 03:16:10 this isn't a router. 03:16:44 "packet" is a term for more than routers, it applies to envelops, message-slips, etc - but ok 03:16:46 I have two devices, one speaks one protocol on physical network X, the other speaks another protocol on physical network Y 03:17:01 alex: OK. I think I understand. 03:17:14 they're completely different methods of exchanging the same content. 03:17:29 This black-box needs to translate everyone from THEM to US to resend ala' THEM-too 03:17:43 just like buying bread in Iran requires a different language and process than buying bread in Germany. 03:17:51 but it's still bread you're buying. 03:18:01 alex: do all devices on a particular interface share the same protocol? 03:18:08 noelhenson: not necessarily 03:18:25 or if they share the same network protocol, the application protocol might be totally different. 03:19:23 So this primary unit is going to take on the burden of being able to talk with everyone? Even though they speak entirely different languages? 03:19:30 yup 03:19:40 So it's special - the others don't have to talk to one another directly? 03:19:42 alex: I see. What about the content. Is it just wrapped in the protocol or is it translated as well? 03:19:59 noelhenson: the content needs to be translated 03:20:24 one protocol might use temperature in F, scaled a certain way, the other might be 10ths of a degree C scaled another way 03:20:45 alex: got it. 03:21:23 Tell us what you haven't liked about your solution candidates so far. You said they all seemed "wrong". 03:21:24 KipIngram: yah, they don't even know that the others are different protocls,.. this box speaks on their behalf. 03:21:29 alex: I can see it as a set of queues. 03:22:12 yep queues/pipes/buffers 03:22:31 Tubes! :P 03:22:35 haha 03:22:45 poppa: I don't think that pipes would be a good solution. It assumes a connection. 03:22:50 Are you ok with translating incoming info into a "common language" and then into the delivery language, or are you trying to avoid double translation? 03:23:13 noelhenson: understood, and he may be lower than I am thinking - the idea is valid. I think C and forth ;-) 03:23:20 "are you ok with" ---> "do you have time for" 03:23:23 alex: for broadcast, I can see this: 03:23:27 KipIngram: I was trying to avoid double translation,. but I think for my solution to be general, I'll just have to. 03:23:55 alex4nde`: sure, you need to be able to take yer common-language and force it down anyone elses throats. 03:23:57 I kind of think so too, but I a lso see why you'd rather avoid it. 03:24:15 inputI/F->inputqueue->normalizer(input translator)->centralqueue->outputtranslator->outputqueue->outputI/F. 03:24:16 PoppaVic: there is 20 years of legacy preventing that from happening. 03:25:03 alex4nde`: well, that's what this gizmo must do: take statements and requests, from all of it - to form statements & requests to the rest of it. 03:25:52 Just out of curiosity, I don't suppose this is a Prophy bus system? 03:27:02 no 03:27:04 --- nick: alex4nde` -> alex4nder 03:32:46 the other option is that I just implement with a specific config in mind, for version v1.0 03:32:49 and see what that teaches me. 03:34:08 alex4nder: I'm sure you'd learn a lot from that. 03:35:29 yah, I bet 80% of it would be obvious by the time v1.0 went to beta. 03:38:01 --- quit: ASau (Read error: 104 (Connection reset by peer)) 03:40:24 --- quit: kar8nga (Remote closed the connection) 03:44:13 --- join: ASau (n=user@83.69.227.32) joined #forth 04:13:10 --- quit: ASau (Read error: 131 (Connection reset by peer)) 04:15:00 --- quit: ASau`` (Remote closed the connection) 04:15:27 --- join: ASau`` (n=user@83.69.227.32) joined #forth 04:21:35 --- join: ASau (n=user@83.69.227.32) joined #forth 04:24:30 --- quit: schme (farmer.freenode.net irc.freenode.net) 04:36:11 --- join: schme (n=marcus@c83-249-82-26.bredband.comhem.se) joined #forth 04:44:54 --- quit: ASau (Read error: 104 (Connection reset by peer)) 04:50:42 --- quit: ASau`` (Read error: 104 (Connection reset by peer)) 04:56:39 --- join: ASau (n=user@83.69.227.32) joined #forth 05:18:44 aoeuaeu 05:18:46 eep 05:19:33 --- quit: ASau (Read error: 110 (Connection timed out)) 05:30:32 --- quit: hiredman (Remote closed the connection) 05:36:14 --- join: kar8nga (n=kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 05:40:57 --- quit: Maki ("Leaving") 05:54:58 --- part: alex4nder left #forth 06:09:38 --- quit: kar8nga (Remote closed the connection) 06:28:24 --- quit: qFox (Read error: 104 (Connection reset by peer)) 06:58:19 --- quit: GeDaMo ("Leaving.") 07:28:17 --- quit: tarbo (Connection timed out) 07:41:27 --- join: ASau (n=user@83.69.227.32) joined #forth 08:03:54 --- join: alex4nder (n=user@dsl093-145-168.sba1.dsl.speakeasy.net) joined #forth 08:04:01 --- join: alex4nde` (n=user@dsl093-145-168.sba1.dsl.speakeasy.net) joined #forth 08:04:06 yoh. 08:04:59 --- quit: alex4nder (Client Quit) 08:07:49 --- join: alex4nder (n=user@dsl093-145-168.sba1.dsl.speakeasy.net) joined #forth 08:08:01 hiccup 08:25:23 Smurfs to the left of me, Smurfs to the right. 08:29:18 oh i totally hate that 08:29:24 they stick to your soles 08:29:35 sticky blue snots 08:29:48 --- part: alex4nde` left #forth 08:29:57 --- quit: alex4nder ("ERC Version 5.3 (IRC client for Emacs)") 08:37:59 --- join: alex4nde` (n=user@dsl093-145-168.sba1.dsl.speakeasy.net) joined #forth 08:38:04 --- nick: alex4nde` -> alex4nder 08:43:17 another use for forth: teaching people how routing tables work 08:43:31 http://www.andern.org/alexander/simrouter.txt 09:07:59 LOL "teaching people how routing tables work' 09:08:29 So, with all these people connected. I'd like to know what you all use Forth for? 09:09:41 ticking off C and C++ programmers? ;-) 09:10:43 pretty much anything that doesn't use strings heavily 09:10:52 and that not many other people have to work on, heh 09:11:57 poppavic: LOL, I have had several of the confrontations in the past. Ask me about development of an assembler for a custom microprocessor sometime... ;) 09:12:16 heh 09:12:20 segher: strings? Forth is excellent at strings. 09:12:35 I used to tick the #asm folks - telling them there was no "asm" language ;-) 09:12:56 poppavic: lmao 09:13:30 mind you, they'd start chanting x86 on a Good Day ;-> 09:19:23 noelhenson: oh really? point me to some nice string package then 09:19:44 i could use one :-) 09:20:22 As you wish... "Library of Forth Routines and Utilities" ISBN 0-452-25841-3 09:20:24 one that doesn't require me to manually allocate space 09:20:51 Also, many articles in Dr. Dobbs Journal (but from about 15 years ago). 09:21:02 hehehe 09:21:20 Or, let me know what you're looking for and I'll look through 25 years of sources and find it for you. ;) 09:21:22 DDJ also published a forth trade-paperback 09:22:13 segher: all strings require allocation. It happens in every language (even asm (if that's a language (in deference to poppavic))) 09:22:22 heh 09:22:31 "asms" I'll buy 09:22:57 not in e.g. Perl 09:23:07 well, strings as arrays, or lists of arrays, stacks of - whatever. still blocks of bytes. 09:23:45 The interpreter is allocating and doing garbage collection for you. As do most modern interpreted languages (eg. ruby, perl, python, php) 09:23:55 awk 09:24:11 OK. I missed that one. 09:24:46 php is a toy, not a language 09:25:30 well, "string" is easy.. I'm never sure wtf people mean by "better" or "string library", etc, etc 09:25:47 segher: LOL. That's what has been said about many modern interpretive languages. 09:25:49 everyone means something else, heh 09:26:00 segher: true. 09:26:36 and then.. THEN.. there is the evil bastich that insists it must include unicode - random utf's - and regex and.. 09:26:39 the way Forth usually represents strings with an address-len pair is excellent 09:26:43 AFAIK, even MS's VisualBasic requires string declarations. 09:26:51 Go does that as well, Go does many things right :-) 09:27:22 taking strings apart is easy as well 09:27:22 segher: true. and with a couple additional words, you can have string variables. 09:27:40 but when i have to paste two (or more!) strings together i get into trouble 09:27:55 The ISBN I provided you with covers old-style BASIC routines like LEFT$, RIGHT$ and MID$. 09:28:14 we have /string and - already, heh 09:28:27 like i said, taking apart is easy 09:28:46 "putting together" makes me wonder WHY? 09:28:54 Putting together is easy as well. Give me an example and I'll tell you what I would do. 09:29:02 because i need to. components in path names, mostly 09:29:11 LL's 09:29:17 teach yer routines to use lists 09:29:33 i *need* to return the final result as _one_ string 09:29:40 but yeah, only the final result 09:30:02 so i could keep an intermediate format, yeah. i'll see how that works out 09:30:03 ah. well, btdthts - I posted the C routines.. The kiddies never look for them ;-) 09:30:21 Ah. Simply create a string variable creation word that includes a maximum size, like 255 (the first byte is the count) 09:30:36 that won't fly 09:30:57 or treat it as a struct, noelhenson - {ct,...,next} 09:31:04 Then create some words like +string that takes ( caddr1 u1 caddr2 u2 - caddr2' u2') 09:31:23 and then what 09:31:42 --- join: Al2O3_ (n=Al2O3@c-75-70-11-191.hsd1.co.comcast.net) joined #forth 09:31:48 have only one "temp" buffer? won't work 09:31:48 recurse or itererate down for total, one malloc/realloc - copy them over and discard coming back the other way 09:31:59 No, no, no. 09:32:09 yeah, but then _all_ your strings need to be in heap memory 09:32:22 so no constant strings 09:32:32 Create a word, say dim$, that creates a string variable and allocates its memory space. 09:32:34 or you need some "magic" way to see if strings are in the heap 09:32:47 well that's just ugly, heh 09:32:51 and wasteful 09:33:01 i want something elegant :-) 09:33:07 No, no, no. I believe that you're thinking more like the way other languages do it. 09:33:13 no 09:33:38 you assume too much 09:33:46 OK. Let me think for a bit and look up some of my old string code. The I have to figure out how to post it here so it look right. 09:33:50 FFI issues 09:33:53 you also assume i haven't thought about this before, heh 09:34:06 merely commo-breakdown 09:34:31 segher: I am making no assumptions beyond what I have (incorrectly apparently) inferred from the convo. 09:34:54 k, great 09:35:37 Also, sorry, dinner time. I'll be AFK for at least an hour. But I do want to continue this conversation. ;) 09:36:14 It's been a pleasant few days ;-) 09:37:23 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 09:37:24 --- nick: Al2O3_ -> Al2O3 10:33:44 --- quit: mathrick (Read error: 104 (Connection reset by peer)) 10:34:08 --- join: mathrick (n=mathrick@dlink214.imada.sdu.dk) joined #forth 10:40:32 heh.. crc used 5bits.. tathi - 6.. ugh and argh ;-) 10:40:50 5 bits? where did I use 5 bits? 10:41:03 crc: I've been reviewing ngaro 10:41:23 well, in between this, that & other 10:41:42 all opcodes are encoded into 32-bit cells 10:41:48 right 10:42:19 and push/pop and "address stack" are the rstack, right? 10:42:24 yes 10:42:28 ok 10:42:53 note: some ngaro implementations have instruction sets beyond the core 31 instructions 10:43:07 yeah, I saw that in the README 10:43:22 I've bot lots more to read on it. 10:43:26 bot/got 11:21:11 --- join: ASau` (n=user@83.69.227.32) joined #forth 11:22:53 --- quit: ASau (farmer.freenode.net irc.freenode.net) 11:22:53 --- quit: schme (farmer.freenode.net irc.freenode.net) 11:23:55 --- join: schme (n=marcus@sxemacs/devel/schme) joined #forth 11:24:17 --- quit: schme (Success) 11:24:19 --- join: schme (n=marcus@c83-249-82-26.bredband.comhem.se) joined #forth 11:53:44 segher: I'm back from dinner. Still want to address strings? 11:54:16 string 'im up! ;-) 11:54:39 Heh... I get that. ;) 11:56:02 'course you do - I pretty much speak jhs/hs english - stumpjumper intonations ;-) 12:00:07 --- join: tarbo (n=me@unaffiliated/tarbo) joined #forth 12:10:09 hey 12:10:18 ho 12:10:18 que tal 12:10:28 (/me learning) 12:10:44 Yes.. it's those cheap thrills 12:14:06 --- join: gogonkt_ (n=info@59.38.200.98) joined #forth 12:26:18 --- quit: gogonkt (Read error: 110 (Connection timed out)) 12:33:08 So... Since segher isn't around, I guess I'll dig out my old strings package and post it on my website. Then we can all beat the hell out of it. :) 12:34:00 heh 12:34:11 --- join: sifbot (n=sifforth@c-68-80-139-0.hsd1.pa.comcast.net) joined #forth 12:34:11 Type sifbot: (or /msg sifbot to play in private) 12:34:17 sounds like fun. Everyone hates everyone elses toolkits ;-) 12:34:48 Works for me. 12:35:52 I think what I always liked about forth and strings was it was so much common-sense. It frightens folks in other languages. 12:36:22 I agree. 12:36:57 my basic parsing funcs in C all reflect forthish words 12:37:10 ..mind you, I prolly should fully rewrite them. 12:37:22 Strings and untyped variables (or rather, coder-enforced types) are kinda scary. But when working with small micros, it's a huge benefit. 12:38:49 I sometimes miss the kaypro and cp/m, the c64, the ts-1000 12:39:22 Yeah, me, too. Is that any indication that when we were both born, there was just rocks? 12:39:48 1960 12:39:53 '62 12:40:02 Yes, I still need work on my flint-knapping 12:40:07 ---older than dirt--- just rocks. 12:40:35 heh 12:40:40 pre-bacteria 12:41:07 My first, I guess you'd call it a hobby CPU board, was the RCA COSMAC ELF I constructed when I was 12 or 13. 12:41:54 My real digital circuit I design and built was a 1KB (yes 1KB) memory expansion for the beast. 12:41:56 I recall them.. I never could afford those play/proto boards. 12:42:28 Gosh, that was like 1977 or something like that. 12:42:59 77 was HS - no $.. then college and work, then work, then the army - it goes on and on ;-) 12:44:27 So now we're reduced to lurking on old-style internet chats about ancient programming languages. Ahem. LMAO 12:45:25 nah, I got my own channel to do that - IRC is my "social time" - face-to-face is tedious, and usually hurts my ears. 12:45:44 rotflmao 12:46:06 besides, "ancient" makes me laugh: if the shit works, it works - a day old or 40 years. 12:46:21 I agree. 12:48:45 Well, I need to sign off and put a few hours into a solar panel controller. 12:49:16 ok. You stay well, chief 12:50:02 np 12:51:33 --- quit: noelhenson ("Leaving") 13:54:30 Ah - I'd wondered how old you were PoppaVic. I was born in '63, so I'm not far behind you. 13:58:18 KipIngram: yah, too old.. But, hell - we all get that way 14:02:22 Yep - some ways you can fight it but other ways you just have to take it in and run with it. 14:02:41 heh, '61. Find a '59-er or a '64-er and we'll have ourselves a straight! 14:02:50 gimp along only ;-) 14:03:52 Geez - midnight already. And I thought I was getting in early tonight. You guys take care; catch you tomorrow. 14:04:00 heh laters 14:04:16 night 14:21:17 --- join: Quartus__ (n=Quartus`@74.198.12.6) joined #forth 14:41:40 --- quit: Quartus` (Read error: 110 (Connection timed out)) 14:46:06 --- quit: Quartus__ (Read error: 110 (Connection timed out)) 14:46:36 --- quit: proteusguy_ (Client Quit) 14:46:49 --- join: proteusguy (n=proteusg@zeppelin.proteus-tech.com) joined #forth 14:48:07 --- quit: proteusguy (Read error: 104 (Connection reset by peer)) 14:48:14 --- join: proteusguy (n=proteusg@zeppelin.proteus-tech.com) joined #forth 14:58:18 --- quit: alex4nder (Read error: 110 (Connection timed out)) 15:32:45 --- join: alex4nder (n=user@dsl093-145-168.sba1.dsl.speakeasy.net) joined #forth 15:34:38 hey 15:41:14 --- quit: PoppaVic (Client Quit) 15:54:54 --- join: kar8nga (n=kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 16:07:49 --- quit: segher ("This computer has gone to sleep") 16:32:37 --- join: noelhenson (n=noel@75-106-241-179.cust.wildblue.net) joined #forth 16:33:41 --- join: xjrn (n=jim@astound-69-42-10-25.ca.astound.net) joined #forth 16:41:40 --- quit: xjrn (Remote closed the connection) 16:47:49 --- quit: noelhenson ("Leaving") 16:57:46 --- quit: alex4nder (Remote closed the connection) 17:32:28 --- quit: kar8nga (Remote closed the connection) 18:55:11 --- quit: ASau` (Read error: 110 (Connection timed out)) 19:04:23 --- join: _dinya__ (n=Denis@90.150.220.27) joined #forth 19:04:34 --- quit: Al2O3 (Read error: 60 (Operation timed out)) 19:05:00 --- quit: _dinya__ (Client Quit) 19:07:24 --- join: _dinya__ (n=Denis@90.150.220.27) joined #forth 19:12:37 --- join: Al2O3 (n=Al2O3@c-75-70-11-191.hsd1.co.comcast.net) joined #forth 19:33:27 --- quit: Al2O3 (Read error: 104 (Connection reset by peer)) 19:33:45 --- join: Al2O3 (n=Al2O3@c-75-70-11-191.hsd1.co.comcast.net) joined #forth 19:37:40 --- join: Al2O3_ (n=Al2O3@c-75-70-11-191.hsd1.co.comcast.net) joined #forth 19:38:17 --- quit: Al2O3 (Read error: 60 (Operation timed out)) 19:38:32 --- nick: Al2O3_ -> Al2O3 19:40:49 --- quit: _dinya__ (Read error: 110 (Connection timed out)) 19:55:28 --- join: dinya_ (n=Denis@89.20.117.45) joined #forth 20:43:55 --- join: DrunkTomato (n=DEDULO@ext-gw.wellcom.tomsk.ru) joined #forth 21:06:13 --- nick: gogonkt_ -> gogonkt 21:41:58 --- quit: proteusguy (Read error: 110 (Connection timed out)) 21:45:00 --- quit: mathrick (Read error: 110 (Connection timed out)) 22:00:02 --- join: kar8nga (n=kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 22:35:13 --- join: Quartus` (n=Quartus`@74.198.8.99) joined #forth 22:45:41 --- join: ASau (n=user@83.69.227.32) joined #forth 22:47:35 --- join: segher (n=segher@84-105-60-153.cable.quicknet.nl) joined #forth 23:18:00 --- join: GeDaMo (n=gedamo@dyn-62-56-89-110.dslaccess.co.uk) joined #forth 23:37:30 --- join: qFox (n=C00K13S@5356B263.cable.casema.nl) joined #forth 23:37:38 --- join: PoppaVic (n=pops@adsl-99-150-133-146.dsl.sfldmi.sbcglobal.net) joined #forth 23:43:03 --- quit: kar8nga (Remote closed the connection) 23:54:29 --- quit: nighty_ ("Lost terminal") 23:55:05 --- join: nighty_ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #forth 23:59:59 --- log: ended forth/09.12.09