michael@stroeder.com wrote:
Full_Name: Michael Ströder Version: HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.84.234)
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.
Example (derived from http://tools.ietf.org/draft/draft-dally-acp133-and-ldap/ using mainly OIDs):
attributetype ( 2.16.840.1.101.2.2.1.69 NAME 'transferStation' EQUALITY 2.5.13.13 ; booleanMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 ; BOOLEAN SINGLE-VALUE )
It would be smarter to just standardize OID macros for each of these OIDs, the way X.500 did, and not require the humans reading these specs to memorize these numeric OIDs...
I don't see any straightforward way to modify our parser as you're suggesting. Unless someone else feels like jumping in, I think we should reject this ITS.