| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | EOT too far... |
BL> If you are going to add SOT/EOT, you may as well add a Tearline BL> at the bottom and *any* kludge PE> That is correct. And what's wrong with SOT as "any kludge"? Nothing. I have no objection to SOT. BL> at the top in *any* position. A blank line would do. PE> Not a blank line, as that would become user-text. Not so. The problem the logic is that it is AREA: or nothing, when an entire message follows. If it was AREA: or a blank line it would be foolproof. The user would never have access to that line, blank or not. PE> Oh, and if the creator of the message puts in a tearline, you PE> STILL don't know for sure at the other end whether it is part PE> of the message or not. Only if it is MANDATORY do you KNOW that PE> it is control information. You still don't understand that a Tearline and EOT are *exactly* the same. I can add a false EOT just as easily and with more damage if I put it near the top. How do you tell a real EOT from a false one? Regards, Bob ___ Blue Wave/QWK v2.12 @EOT: ---* Origin: Precision Nonsense, Sydney (3:711/934.12) 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™.