> It might be helpful if the schema config file parser would accept lines with
> comments at the end separated by semicolon.
The parser doesn't know anything about line endings. Remember, lines with
leading white space are continuations of the previous line. The schema parser
is just fed a single string as one long line, the line endings were removed
long before it ever got there.
Maybe lines with ; could be truncated before passing it to the schema
parser? I don't know if that has any impact on processing slapd.conf in
general. The slapd.conf parser has to already know in advance that this
part is a schema declaration (started by key-word objectclass etc.) and
could change pre-processing?