00:00:00 --- log: started forth/06.10.24 00:19:10 --- quit: arke (Read error: 60 (Operation timed out)) 01:00:37 --- join: arke (i=Chris@x25.vpn.hrz.tu-darmstadt.de) joined #forth 01:00:46 --- mode: ChanServ set +o arke 01:43:44 --- join: vatic (n=chatzill@pool-162-84-156-148.ny5030.east.verizon.net) joined #forth 02:12:03 --- quit: arke (Read error: 110 (Connection timed out)) 04:24:13 --- join: crest_ (n=crest@p54896874.dip.t-dialin.net) joined #forth 04:25:34 morning 04:26:11 --- quit: Crest (Read error: 145 (Connection timed out)) 04:28:13 --- nick: crest_ -> Crest 04:32:34 --- join: TreyB (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 04:32:34 --- quit: TreyB_ (Read error: 104 (Connection reset by peer)) 04:36:20 --- quit: neceve (Read error: 145 (Connection timed out)) 04:39:33 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #forth 06:02:02 --- join: Ray_work (n=Raystm2@199.227.227.26) joined #forth 06:02:37 Good morning. 06:03:43 --- quit: vatic ("*poof*") 06:27:22 --- join: madwork (n=foo@204.138.110.15) joined #forth 06:28:10 --- nick: Raystm2 -> nanstm 06:57:27 --- join: zpg (n=user@soup.linux.pwf.cam.ac.uk) joined #forth 06:57:29 hi guys 06:57:45 --- quit: jeremy_c (Read error: 145 (Connection timed out)) 07:09:32 --- quit: madwork (Read error: 104 (Connection reset by peer)) 07:10:59 --- quit: neceve (Read error: 145 (Connection timed out)) 07:22:29 Hi z 07:24:13 greetings Ray 07:24:32 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #forth 07:24:57 Whats going on this morning? 07:25:03 anything? 07:26:09 the afternoon's shunted it aside. 07:26:23 that aside, little in the way of excitement here. nice day though/ 07:27:41 okay, a request -- does anyone know of a really good essay / article / book chapter (perhaps in Thinking/Brodie) that covers factoring really well? 07:28:12 i've been concentrating on building up a vocabulary, but i think i need to pay more attnetion to factoring before losing the plot entirely :) 07:28:16 Hmmm,... 07:28:52 * Ray_work got a customer, please stand by for I don't know what... 07:29:33 * zpg leans on his cane. 07:34:19 hmm, on closer inspection, thinking forth seems to be my best bet. time to see if i can print this out. 07:46:51 --- join: madwork (n=foo@204.138.110.15) joined #forth 07:47:04 Ya, thinking is great about factoring. But for _the_ factoring referance, I don' t know that there is one. Might be neat to do a site about factoring in forth, some of the pitfalls that some suffer... 07:47:23 it's a mad mad world, Hi madwork! :) 07:49:40 Hi again. 07:51:49 Ray_work: yes, a site or reference on the wiki would be nice. having said that, if Brodie is THE reference, it's often better to sit down with the book and consult a forum/discussion group once the basics are there. 07:56:20 right, time to push off. talk soon. 07:56:28 cheers for now 07:56:29 --- quit: zpg ("ERC Version 5.0.4 $Revision: 1.726.2.19 $ (IRC client for Emacs)") 07:56:38 --- join: jeremy_c (n=jeremy_c@cpe-71-74-145-210.neo.res.rr.com) joined #forth 07:57:00 When gforth says it uses GCC to compile... will it create a stand alone executable file from my forth code? 07:59:14 --- join: erider (n=erider@unaffiliated/erider) joined #forth 07:59:24 good morning all 08:02:00 jeremy_c: it can. 08:02:30 Ray_work: do you know how? gforth --help and the man page for gforth doesn't seem to be telling me, unless I'm blind. 08:02:45 The process is called "TURNKEY"-ing a program 08:04:18 jeremy_c: I don't have my programming resources here at the caster store where I work, and I tend to be busy here thru the day, so please be patient with me, ok? :) 08:04:41 Ray_work: absolutely not! It is unacceptable!!! 08:04:46 :-D 08:04:50 looking for the gForth TURNKEY :) hehehe 08:04:57 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-132-028.pools.arcor-ip.net) joined #forth 08:05:03 --- quit: larsb (Read error: 110 (Connection timed out)) 08:05:12 Ray_work: I am looking right now for that word. didn't recognize it. 08:05:19 was looking for compile, executable, etc... 08:05:52 hi jeremy_c 08:05:59 erider: howdy. 08:06:09 spent a few hours with forth last night, playing some more with it today. 08:06:11 have you look at chicken? 08:06:17 erider: no. 08:06:58 hmm dbases that is intense 08:08:00 --- join: snowrichard (n=richard@12.18.108.162) joined #forth 08:08:12 --- join: larsb (i=lars@1-1-14-10a.kt.gbg.bostream.se) joined #forth 08:10:18 With a cursor glance over the table of contents of the gforth manual at http://www.delorie.com/gnu/docs/gforth/gforth.html#SEC_Top I don't see the turnkey stuff yet... but, not giving up. 08:10:34 s/cursor/cursory 08:12:39 You can make a turnkey image by letting 'cold execute a word (your turnkey application) that never returns; instead, it exits Gforth via bye or throw. 08:12:44 http://www.delorie.com/gnu/docs/gforth/gforth_251.html 08:13:12 cool. 08:13:13 thanks. 08:13:35 * jeremy_c still doesn't see how it works though. 08:13:47 Ray_work: but you don't have to answer it, your at work. 08:13:54 hold for Quartus to arrive, he's actually done this thing. 08:14:11 why would throw exit the application 08:14:18 unless the catcher does a bye 08:14:26 I haven' t done a turnkey ap yet. All my stuff are just extentions to the interpreter/compiler so far. 08:14:43 does gforth have a deferred word called default ? 08:14:50 I440r: Mark, I suppose that's just what happens. 08:15:12 in isforth you would do ' my-app-main is default turnkey my-app 08:15:13 I don't know yet, checking word list... 08:15:29 im going to work but will be back on from there 08:15:30 :) 08:15:43 cool, see ya soon, safe travel. 08:21:21 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 08:21:26 --- nick: snoopy_1711 -> Snoopy42 08:29:19 --- quit: madwork (Read error: 104 (Connection reset by peer)) 08:36:35 back 08:40:52 hi I440r 08:41:59 so do you guys really think forth makes your life easier as a programmer? 08:42:19 Coming form algo related languages, forth seems pretty cumbersome. 08:43:44 --- join: madwork (n=foo@204.138.110.15) joined #forth 08:44:15 true . \ -1 is pretty funny to me. 08:47:05 --- quit: snowrichard ("Leaving") 08:55:06 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 08:57:07 hi virl 09:06:20 hi 09:09:44 --- join: JasonWoof (n=jason@c-71-192-26-248.hsd1.ma.comcast.net) joined #forth 09:09:45 --- mode: ChanServ set +o JasonWoof 09:31:14 jeremy_c, definatly. forth is alot easier to code in than anything else i code in :) 09:32:25 I gave up trying to figure out the fibonacci quiz. Guess I need to re-read my stack operations. Kept getting underflow or overflow :-/ 09:34:07 I'm seeing how it performs small tasks well, but I guess the implementation of factoring is still puzzling me. The idea is great. I am sure it's due to my lack of forth knowledge at this point. I cannot take a simple task and see how forth would handle it. 09:34:24 s/implementation/action/ 09:35:10 brb 09:35:22 at the moment im doing exactly the opposit of factoring my (ppc32 asm) code in order to get the max performance 09:35:30 out of cast-256 09:57:12 --- join: nighty__ (n=nighty@sushi.rural-networks.com) joined #forth 09:59:35 --- quit: nighty_ (Read error: 145 (Connection timed out)) 10:29:37 hey 10:30:20 HI Quartus 10:30:56 Vx track via ups arrival date 25th 10:31:02 Neat-o. 10:36:04 hi Q 10:36:09 Hey. 10:36:59 brb snack cake time 10:38:35 sugar free? I'll have one erider, fax it to me. 10:42:13 Ray_work: sorry it has sugar ray 10:43:44 sugar ray robinson or sugar ray leonard? 10:44:12 lol 10:44:34 Sugarless Ray St. Marie! darn it! 10:45:37 oh and I havent had a ciggy since 8 am. This is the longest I,' 10:45:43 ve ever gone . 10:45:47 Gforth won't make .exe files. It can make binary application images, even portable ones, but you use gforth to launch'em, or let it launch gforth for you with the #! stuff at the start. 10:46:10 --- quit: jeremy_c (Read error: 110 (Connection timed out)) 10:47:39 Quartus they are not thinking outside the box lol 10:48:08 I'm not sure what you mean. 10:48:59 its a joke 10:49:05 Ok. 10:49:53 erider, I won't fit in the box so outside I remain, are you saying I don't think? Put up yer dukes! :) 10:50:10 * Ray_work knows it's true. 10:50:13 because forth most of the time is an environment language well there are exception ie Quartus for palm :) 10:50:35 Environment language? You mean it's the OS? 10:50:44 yes 10:50:57 let lisp 10:51:12 I'm willing to bet that it is more embedded the OS and is in all manner of device and convenience. 10:51:23 the+n 10:52:02 I think that's the exception rather than the rule nowadays. Gforth, SwiftForth, Win32Forth, Quartus Forth, BigForth, iForth, isForth, kForth, Carbon MacForth, RetroForth all are hosted. RetroForth has/had an OS-type version. 10:52:58 It's the only one I can think of that has a non-hosted version. Forth, Inc.'s SwiftX embedded stuff is umbilical. 10:54:03 Ooh cool, leaves a bootable, runnable image on the slave device then? 10:54:30 With just the required components. 10:54:50 neat. 10:55:43 they operation within themselves which make them environment languages however that can communicate outside of that environment but they can't be packages into a runable binary like quartus can do on palm 10:56:04 s/that/they 10:56:22 SwiftForth can. Win32Forth can. RetroForth can turnkey to an executable under Linux, at least. I don't know about the others. 10:57:06 so most can't? 10:57:12 I don't know about the others. 10:57:22 I see 10:58:11 I consider it unimportant; on desktops you can feed the source to the Forth engine and you're up and running; compiliation speeds in Forth are really, really fast. 10:58:54 Gforth's application-image setup lets you start up even faster; precompiled source. 10:59:57 There's no reason any given Forth can't be made to generate an executable, not from a technical perspective anyway. 11:01:19 I think that would be a nice feature to add. What do you think? 11:01:32 To add to what? 11:02:46 I don't think it's terribly important to be able to produce a stand-alone executable from forth source 11:02:49 in most cases anyway 11:03:02 if you want that ability, code it, or use a forth that does that already 11:03:03 to be able to generate executable code 11:03:14 It was important on the Palm, but on desktops I agree; it's less of a requirement. If you require it, there are Forths that do it. 11:03:36 It's a Forth- and OS-specific undertaking. 11:04:02 mmm... good point on the palm os 11:05:00 JasonWoof: what was the point on the palm 11:05:11 that it's important to have stand-alone 11:05:32 there is no why 11:05:43 just that it was important 11:05:45 desktop software usually comes with a bunch of files anyway, and I have no problem with the interpreter being one of them 11:05:54 There are programming languages on the Palm where you need to keep the compiler on there to feed the source, or P-code to. There's DragonForth that bundles the entire Forth kernel inside every 'stand-alone' PRC it makes. Quartus Forth recursively extracts only the application-specific code. 11:06:47 It's a native-code compiler, and it was designed to be able to do this practically. 11:07:02 now that is neat 11:07:09 that being said, the only major disadvantage of having the ability to create stand-alone apps is that people can then easily hide their source code 11:07:29 JasonWoof, I suppose. You could shroud your Forth. 11:08:16 Gforth's application images hide the source quite nicely. 11:08:33 or write something for someone else to use that doesn't have forth installed 11:09:06 erider, if you write it for them in, for instance, perl, they need perl. 11:09:55 true but perl is a scripting language but there are perl compilers that make executable out there 11:10:13 And there are Forth compilers that make executable code out there. 11:10:25 agreed 11:10:44 'scripting language' is a vague term, at any rate. 11:11:05 I was just giving you the definition of an environment language 11:11:31 I'm not arguing with you about forth :) 11:29:00 I plan on releasing my forth apps along with a copy of the forth compiler/interpreter 11:29:39 at least for windoze and mac 11:31:59 well, the problem isn't to haven't the source, the problem is to get the source. 11:48:48 heh? 11:50:08 seems like it just ended there :) 11:50:15 is not to get the 11:50:20 ehm.. 11:50:34 the problem is to not to get the source 11:52:58 what's the problem? 11:53:01 I mean when you have a way to switch easily betwen different views of code then you don't really need one seperated view like source code. 11:54:10 (according to your argument about stand-alone apps and that people can hide their source) 11:59:48 --- join: Raystm2 (n=NanRay@adsl-69-149-61-49.dsl.rcsntx.swbell.net) joined #forth 12:03:18 Set up a custom search engine: http://quartus.net/search/ 12:03:20 Let me know what you think. 12:05:48 --- quit: nanstm (Read error: 110 (Connection timed out)) 13:01:18 --- join: mark4 (n=mark4@67.135.84.40) joined #forth 13:18:39 --- quit: I440r_ (Read error: 110 (Connection timed out)) 13:28:20 --- join: EdLin (n=vim@as5300-6.216-194-21-252.nyc.ny.metconnect.net) joined #forth 13:29:47 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/") 13:56:57 --- join: cmeme (n=cmeme@boa.b9.com) joined #forth 13:56:57 --- quit: cmeme (Remote closed the connection) 13:57:54 --- join: kmr (n=user@70.88.163.233) joined #forth 13:57:58 --- join: cmeme (n=cmeme@boa.b9.com) joined #forth 14:05:22 --- part: EdLin left #forth 14:27:42 --- join: arke (n=Chris@pD9E050B0.dip.t-dialin.net) joined #forth 14:27:42 --- mode: ChanServ set +o arke 14:36:31 pizza time 14:51:09 --- join: I440r_ (n=mark4@67.135.84.40) joined #forth 14:54:53 --- quit: mark4 (Read error: 110 (Connection timed out)) 15:00:18 --- quit: Ray_work (Read error: 131 (Connection reset by peer)) 15:04:36 --- join: Amanita_Virosa (n=jenni@adsl-69-154-191-166.dsl.hstntx.swbell.net) joined #forth 15:12:23 --- join: tathi (n=Joshua@pdpc/supporter/bronze/tathi) joined #forth 15:12:23 --- mode: ChanServ set +o tathi 15:19:46 --- join: jackokring (n=jackokri@static-195-248-105-144.adsl.hotchilli.net) joined #forth 15:37:05 --- quit: jackokring (Read error: 145 (Connection timed out)) 15:58:44 --- quit: tathi ("Leaving") 15:59:48 not very busy today hmm..... 16:24:43 tathi was here ? 16:24:45 eep! 16:24:59 so he was. 16:25:28 let me know what you think of the Forth search engine I put up -- http://quartus.net/search 16:25:50 where does it search ? 16:26:01 It's a tuned google search. Searches all over the ding-dang place. 16:26:14 don'cha'know. 16:34:25 If you search for something and you don't see a site you think should be there, let me know. 16:35:25 sure :) 16:35:35 looks good so far, have to play with it more later 16:36:30 --- quit: erider (Read error: 110 (Connection timed out)) 16:37:13 --- join: erider (n=erider@unaffiliated/erider) joined #forth 16:45:29 quiet night tonight 16:45:40 Happens. 16:46:00 SCREAM 16:46:09 better? 16:48:29 hmm 16:49:12 --- quit: segher (Nick collision from services.) 16:49:26 --- join: segher (n=segher@dslb-084-056-177-246.pools.arcor-ip.net) joined #forth 16:55:28 --- quit: I440r_ ("Leaving") 17:00:25 --- quit: Amanita_Virosa ("Blamo") 17:45:32 --- join: snowrichard (n=richard@12.18.108.162) joined #forth 17:48:54 --- topic: set to 'Welcome to #forth. We discuss the Forth programming language, simplicity, and a variety of technical subjects. Introduction: http://tinyurl.com/kvawv | Starting Forth: http://tinyurl.com/rm7pq | Thinking Forth: http://tinyurl.com/nsy4j | Gforth compiler: http://tinyurl.com/s8uho | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | Search engine: http://quartus.net/search | Pas' by Quartus 17:49:10 --- topic: set to 'Welcome to #forth. We discuss the Forth programming language and a variety of technical subjects. Introduction: http://tinyurl.com/kvawv | Starting Forth: http://tinyurl.com/rm7pq | Thinking Forth: http://tinyurl.com/nsy4j | Gforth compiler: http://tinyurl.com/s8uho | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | Search engine: http://quartus.net/search | Pas' by Quartus 17:49:17 mutter mutter 17:49:45 --- topic: set to 'Welcome to #forth. We discuss the Forth programming language and a variety of technical subjects. Introduction: http://tinyurl.com/kvawv | Starting Forth: http://tinyurl.com/rm7pq | Thinking Forth: http://tinyurl.com/nsy4j | Gforth compiler: http://tinyurl.com/s8uho | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | Search engine: http://quartus.net/search | Paste >5 lines:' by Quartus 17:49:54 grr. 17:50:12 --- topic: set to 'Welcome to #forth. We discuss the Forth programming language and a variety of technical subjects. Introduction: http://tinyurl.com/kvawv | Starting Forth: http://tinyurl.com/rm7pq | Thinking Forth: http://tinyurl.com/nsy4j | Gforth compiler: http://tinyurl.com/s8uho | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | http://quartus.net/search | Paste: http://forth.pastebin.ca' by Quartus 18:01:19 --- quit: virl ("Verlassend") 18:01:48 --- quit: snowrichard ("Leaving") 18:24:26 --- quit: erider (Read error: 110 (Connection timed out)) 18:25:51 --- join: crc (n=crc@pdpc/supporter/active/crc) joined #forth 18:25:51 --- mode: ChanServ set +o crc 18:45:28 * Crest is away: … 19:23:40 Awww, man. No ##cobol or #cobol. Suc0rs. 19:23:45 Sux0rs, even. 19:29:56 Probably no #rpg or #rexx, either. 19:34:33 I have a file that was apparently produced by a COBOL program that I need to parse. It uses COMP-3 encoding, but has some oddities. I was hoping to asking a COBOL freak. 19:40:14 I had to do some COBOL work at one time, but I doubt I could shed much light. 19:48:59 These fields are defined as S9999999V99, and have numbers like 00000000{ and 000000013C and 00000438F 19:49:13 I'm finding comflicting information on what the COMP-3 format is. 19:49:27 The C is positive (usually), and the F is negative 19:49:46 But there's also an I at the end of a couple, and { is not defined that I can locate. 19:49:48 BCD format, as I recall. 19:49:53 Yah 19:51:32 How are you getting { out of a BCD digit? 19:52:59 Or C or F for that matter? 19:53:27 It's the ASCII value. There are 9 characters in each field. They all either end in C, F, I or { 19:53:59 EBCDIC, I assume you mean. 19:54:12 And C and F are legal in packed BCD, as far as 4 bits per character go. 19:54:15 Or is this post-conversion? 19:54:59 I suspect it's post conversion. I have little information on the file format, other than the fields are specified as S9999999V99, and I've backtracked this to COBOL PIC formatting. 19:55:35 Hrm, Comp-3 is a binary format, so if somebody's helpfully converted it to ASCII first, I suppose it's possible the data is not in its original format. 19:55:47 9000000300000451I00000013C00000000{00000000{00000000{00000000{00000000{00000438F00000000{00000000{00000438F1000000000000000000000000000000000000000 19:55:53 That's an original record. 19:56:00 Ok. That's not packed BCD, so those aren't comp-3. 19:56:06 Here's one broken down according to the document. 19:56:16 9-0000003-00000451I-00000013C-00000000{-00000000{-00000000{-00000000{-00000000{-00000438F-00000000{-00000000{-00000438F-1-0000-0000-000000000-000000000-000000000-0000 19:56:26 I've inserted the -'s to indicate field breaks. 19:56:46 I think they were COMP-3. 19:56:54 And this is the ASCII representation of it. 19:56:56 Whatever they were originally is moot at this point, if that's what you're working from. 19:57:32 No, it's not moot, because I need to know what produced the original fields to know how to parse these. 19:57:58 Not if they've been unpacked and converted from EBCDIC->ASCII. You'd have to know the details of that conversion process as well. 19:58:12 http://www.simotime.com/dataen01.htm 19:59:41 As you can see, the COMP-3 fields are packed BCD. What you have there is not packed BCD, so it's not COMP-3, not at this stage anyway, if it ever was. 20:01:20 Fine. The document I have specifies the fields as S9999999V99, and searching for that string produces a lot of results indicative that it's COMP-3 format. So somehow, we get from a COMP-3 field to this representation. 20:01:36 Much of it is consistent with what I've read, EXCEPT for the { and I trailing two of the fields. 20:01:44 The C indicates a positive number. 20:01:44 S9999999V99 is a PIC format specifier; it doesn't dictate the storage format. 20:02:14 USAGE specifies the storage format. 20:02:30 And the ones I've found for S9999999V99 all use have USAGE COMP-3 20:03:26 Well, that's common, because it took less space. But what you're showing there is in no way packed BCD. 20:04:04 At this points, it appears to be unpacked BCD. 20:04:59 Not if it's displaying 0 and '0'. A '0' character is $30 in ASCII, $F0 in EBCDIC. In BCD, it's $00. 20:05:08 BCD is a binary format that is neither ASCII nor EBCDIC. 20:06:09 I'm quite familiar with BCD and packed BCD. I use it all the time. It's unpacked into ASCII. 20:06:19 $00 is $30 $30 20:08:05 It can be unpacked into any representation. What steps have been applied in this case, I don't know. { might be the original $7B from a USAGE COMP number, untranslated. 20:08:42 Guessing that somebody's taken the binary format and helpfully partially converted it. 20:08:48 Sarcasm on the 'helpfully'. 20:13:35 I doubt they put too much work into this. It likely is the minimum work needed to get it from how ever it was stored on this likely COBOL based system into something they could export. The rules for conversion are likely simple, and should be able to be derived. We can tell that 451-438=13. We know there are 7 digits to the left of the decimal point (implied or actual) and 2 to the right. 20:13:43 CHeck this out: http://www.discinterchange.com/TechTalk_signed_fields_.html 20:15:32 So I in EBCDIC is $C9, so that's a 9 digit, OR'd with a positive flag. 20:16:16 So it does look like a half-baked conversion to ASCII. 20:16:49 I saw that site, and two other articles on it, but not that one. I think that explains it. 20:16:54 F is $C6 in EBCDIC, so that's a 6 digit OR'd with a positive flag ($C0). 20:17:32 And that's consistent with the I in the 13I field, also. 20:17:46 So you may encounter A through I for positive last-digits. 20:17:54 And we see I. 20:18:07 } and J-R for negative last-digits. 20:19:09 So we have 9 0's in several of them, 133 (or 1.33) in another. 4386 (43.86) in another, and 45.19. And all the math still works. 20:19:41 It appears they should all have a non-numeric final digit. 20:20:01 If they're all in the same USAGE with S9999999V99. 20:23:02 Yea, they are. For the values that are dollar amounts. 20:23:20 Some of the others are just plain numeric fields and don't require special treatment. 20:23:49 Basically, a simple lookup table takes care of the last character for conversion. A trivial C program :) 20:27:15 Trivial in Forth too. I'd compute it. 20:27:45 So some knuckleknob somewhere converted 8 digits for you, and then left the last one in its original binary format. 20:28:11 Which at least was a printable ASCII character. 20:28:17 That's called luck. 20:28:17 But yea. 20:28:51 lookup or compute. It's so trivial that the method doesn't really matter. 20:31:52 In Forth: : convert-last ( char -- flag digit ) dup 15 and swap 16 and 0<> ; 20:32:12 :) 20:32:16 flag indicates negative or not. 20:33:14 I have no idea how to precess stdin in forth. 20:33:27 In gforth, you read from stdin. 20:34:09 In stdin, gforth reads from you! 20:34:12 as in ... stdin read-file 20:34:13 Wait, wrong meme. Sorry. 20:34:19 heh 20:34:35 So it's pretty straightforward. 20:47:25 I picked up 2 IBM T40 laptops today. 1.5Ghz/40GB/256MB (shortly to be 768MB), 10/100/1000 ethernet, 802.11b, 14.1" 1024x768, CDRW/DVD. Nice little machines. 20:47:46 Neat. 20:48:07 Guy at work, his wife works for ADP. Every couple years, they do a wholesale replacement of all machines. 20:48:13 Auction off the old ones. 20:48:32 Oooh, and they have a 56K modem built in! 20:48:57 For when you need that flashback to the olden days. 20:49:16 heh 20:52:48 --- join: dibblego (n=nobody@CPE-61-9-214-69.qld.bigpond.net.au) joined #forth 20:54:52 Time for bed. Thanks for your help! 20:55:00 sure. Ciao! 21:16:57 --- quit: Jim7J1AJH ("leaving") 21:45:41 good night :) 21:46:40 goodnight 22:00:01 --- join: Jim7J1AJH (n=jim@221x115x224x2.ap221.ftth.ucom.ne.jp) joined #forth 22:13:39 --- join: arke_ (n=Chris@pD9E04C9E.dip.t-dialin.net) joined #forth 22:21:25 --- quit: arke (Read error: 145 (Connection timed out)) 22:34:40 --- nick: arke_ -> arke 22:50:44 --- join: TreyB_ (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 23:04:59 --- quit: TreyB (Read error: 110 (Connection timed out)) 23:27:54 --- quit: arke (Read error: 110 (Connection timed out)) 23:41:36 --- join: arke (n=Chris@x79.vpn.hrz.tu-darmstadt.de) joined #forth 23:41:36 --- mode: ChanServ set +o arke 23:47:03 --- quit: dibblego ("Leaving") 23:59:59 --- log: ended forth/06.10.24