newlines and #comments in httpd parse.y

[gwes]

An accidentally unterminated string in httpd.conf results in
the famed yacc "syntax error" message.
For instance:
     root "/
    }
}


#   "hi" <- line xx: syntax error

The loop starting at line 1515 in httpd parse.y
     }

        switch (c) {
        case '\'':
        case '"':
                quotec = c;
will uncomplainingly eat -anything- up to the matching quote
character even in a comment line.

The resulting error message usually a very long way from
the actual mistake.

Would a change to terminate the string with an error at the
next newline be appropriate? Should quoted newlines be allowed?
Should # comments be allowed and elided, included verbatim,
or cause an error?

I can provide a patch for any of those cases.

geoff steckel