From: Brian I. <in...@tt...> - 2002-01-19 16:36:52
|
On 19/01/02 09:23 -0500, Clark C . Evans wrote: > | At any rate, attached is the latest spec. It includes > | "everything", but there are problems with it. > > Way cool. This is checked into CVS and is now > accessable via HEAD at [1]. > > | this: ]- > | normal value, > | # an empty lines > | > | # Another comment > | ... > | > | A streaming API would want to send the empty line to > | the application before it deals with the comment (it > | would want to send the comment too, for an editor...). > | However it wouldn't know whether it is content or > | comment. > > Ahh. In the (modified) case above, it must "chomp" > the empty line, but it can't determine this till > the comment is processed. Ok. Got it. Ick. > Let me chew on it for a while... There will obviously be different parser interfaces. A line by line interface would have no problems here. An interface used by a loader wouldn't care about comments. A push interface could report comments early. I'd like to know the _exact_ use case that is driving this. For whom is this causing a problem? Cheers, Brian |