Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA18772; Mon, 11 Mar 1996 16:34:02 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.4); Mon, 11 Mar 1996 16:33:16 -0500 Received: from po10.andrew.cmu.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id QAA18716; Mon, 11 Mar 1996 16:33:14 -0500 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.7.4/8.7.1) id QAA00963 for drums@cs.utk.edu; Mon, 11 Mar 1996 16:33:10 -0500 Received: via switchmail; Mon, 11 Mar 1996 16:33:09 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 11 Mar 1996 16:32:37 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 11 Mar 1996 16:32:36 -0500 (EST) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 11 Mar 1996 16:32:35 -0500 (EST) Message-ID: Date: Mon, 11 Mar 1996 16:32:35 -0500 (EST) From: John Gardiner Myers To: drums@cs.utk.edu Subject: Re: Free insertion of linear-white-space In-Reply-To: <199603112107.QAA22282@wilma.cs.utk.edu> References: <199603112107.QAA22282@wilma.cs.utk.edu> Keith Moore writes: > Along more general lines, I'd like to see the 822 grammar very clearly > indicate what is and is not a structured field. I've already defined unstructured ::= *text > If this means explicitly adding tokens to the grammar that indicate where > white-space and/or comments can be inserted...well, that's ugly, but at > least it's unambiguous. Not only is this ugly, but there's a problem with then having to update other documents, such as MIME, that define structured fields. > But the 822 ABNF gets used both for cases where white space and comments are > legal between tokens and for cases where they are not legal, and having to > specify which case is which in text is getting to be a pain. I'd say it's the single most painful, complicated part of 822. But at this point, our options are limited. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up