| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | 4x16meg Simms 4 Sale |
Hi, Bob. BL> FM> Hi, Bob. (Written in the blank line you *still* haven't BL> FM> explained.) BL> I like a blank at the top. I can see that, matches your head. BL> Why don't you leave a blank line at the top? There's far too many blank lines in this universe already; YOU'RE compounding the problem, I'm not about to. BL> BL> BTW, how do you know where to add your EOT? Read the Tear line, BL> BL> do you? If that's the case, what's it doing that the Tear line BL> BL> doesn't do? Your EOT logic is loony. BL> FM> Actually, that's a very good point. If an automated process can BL> FM> determine where to place a SOT/EOT pair, then by trivial proof BL> FM> a SOT/EOT pair ain't necessary. BL> ROFL!! I was beginning to think it was me... BL> I don't mind people clogging up a system with pointless duplication BL> as long as it's easy to remove. The SOT is easy; just read down the BL> message until you run out of #1 lines, it's just one more... but the BL> EOT needs an additional step that slows the whole process. You have to BL> find it so you can remove it! It's only purpose is to be removed! I have concluded that a SOT is necessary in one rare circumstance (and therefore should be present in a much larger set of not-so-rare circumstances at least) and that EOT is never necessary. See my long message to Paul for the justification, and of course I'd be interested in your comments too. BL> For the life of me, I can't see why Paul can't see how fucking BL> useless it is! It's supposed to define the end of the text. but it has BL> to be insereted inside the tear line. Why not use the tear line? His BL> argument is that the tear line is not compulsory. But neither is EOT!! I agree with that. BL> And exactly the same loony logic applies at the other end with SOT. BL> SOT is the last #1 kludge line; so is the one before. ROFL. If there BL> are no kludge lines, then SOT has some value. It prevents a non-point BL> lunatic adding his own #1 kludge line in Netmail at the head of his BL> text, to post it untraceably in another echo, say. No, SOT is needed in one case, and not to stop loonys either. BL> But it assumes a lunatic bent on stuffing the system to give SOT any BL> value at all, and personally as a certified and fully accreditied BL> lunatic, I'd just use Hexedit and change the address too. There is another, valid, reason for SOT. Regards, fIM. * * Time is an illusion. Lunchtime, doubly so. @EOT: ---* Origin: Pedants Inc. (3:711/934.24) SEEN-BY: 711/934 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.