On 01/12/02 10:53 +0200, Oren Ben-Kiki wrote:
> Brian Ingerson wrote:
> > The problem I was not seeing is that commented out lines must start with
> > '# ', not just '#'.
> Right. Personally, I never leave out the space after a comment '#' (or, for
> that matter, after '//' or '/*'). Obviously that's not a universal style.
> > Would someone please remind me why this is necessary for full
> > line comments?
> We definitely wanted to allow:
> url: domain.tld:/some/path#fragment
> This means that '#' would only start a comment if there were spaces involved
> somehow. We already have the notion that some characters are onlyindicators
> if followed by a space (e.g. ',', ':'). Then we considered things like
> Smalltalk #symbols. It made sense to make '#' a "space indicator", so the
> comment marker became '# '. That's actually not quite accurate because the
> '# ' must be either at the start of a line or be preceded by a space, so '#'
> still remained something of a special case.
> > This is going to cause no end of grief, I'm sure. I would propose that
> > we allow non-trailing throwaways to not require the space after the '#'.
> I think it would be confusing to have one set of rules for trailing comments
> and one for non-trailing ones. For example:
> not comment: #symbol
Well I disagree. But I think I'm willing to drop my argument. We can
keep it as is. It would be nice if parsers could detect this kind of
thing and print a useful message.