[Date Prev][Date Next]
Re: (ITS#5662) Comments in schema declarations separated by semicolon
> Full_Name: Michael Ströder
> Version: HEAD
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (188.8.131.52)
> 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.8184.108.40.206.2.1.69 NAME 'transferStation'
> EQUALITY 220.127.116.11 ; booleanMatch
> SYNTAX 18.104.22.168.4.1.1422.214.171.124.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.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/