PE> According to most, not all.
 
 BL>   I only know what I read in the specifications. FTS4 says that is
 BL> "not required by all processors... is added to ensure
compatibility."
 PE>  ^^^^^^^^^^^^                       ^^^^^^^
 BL> Where does it say anything about optional? 

 PE> "which bit of 'not required' do you not understand" is what
 PE> they say.

  What part of "is added" do they not understand?

  But I know what you are saying. A specification has to be written as
if by god, perfectly clear. Until after WWII, treaties were written in
French rather than English, because English is not a precise language.
English can only be clear in short sentences without commas.

  His problem is that he tries to explain. A specification defines.

 BL> Try writing a reader and discover the sequence for yourself.

 PE> FREQ MSQ335.ZIP from 3:711/934.

 BL> If you wrote one and learned nothing about the uselessness of
 BL> EOT, there is no hope for you.

 PE> So much for your theory about "try writing a reader", as if
 PE> only people who had written one could know, and you know damn
 PE> well that hardly anyone has the time to do that to prove you
 PE> wrong. What a shame that blew up in your face.

  You think because you are childish, everyone plays childish games.
And you did not answer the question, either. There is a sequence, and
the EOT part of that sequence is additional, and immediately
discarded because it has no reliable meaning. I was merely trying (and
failing) to get your closed mind to look at it from the other end.

 PE> I know that there is no tearline or origin line generated by
 PE> the QWK reader, since they are fido kludges

  Don't you count BlueWave as a QWK reader, then? It generates a tear
line, dorko.

 PE> Poor old, Bob. At least have the courtesy to apologize after
 PE> you find that the code doesn't do anything as ridiculous as
 PE> that.

 BL> The only place your SOT/EOT can possibly work is in the
 BL> original message, when the AUTHOR knows where his message ends.

 PE> That is correct.

  Apology, for what?

 PE> No, it doesn't fuck up because of that. Rod is welcome to send
 PE> me two origin lines with PQWK260. I don't care. I do care when
 PE> he was using <260 though, because of a bug in PQWK.

  I see. You define a bug as anything that fucks SOT/EOT. You wrote
PQWK to add SOT/EOT and eliminate problems with kludge lines in the
text, but it didn't. Now it does. Or does it?

 PE> k and a qwk2pkt, no. Actually I didn't write them, I took over
 PE> development of them, adding the SOT/EOT support.

  And your SOT/EOT didn't work, did it? 

  But it was only a bug.

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---