> I think having an established syntax for private link properties is > needed. I don't think we should add things like "nports" as reserved > field name, as those names set probably would be expanded even further > while more and more classes of links are supported.
Would those names have to start with an underscore? Could we reserve the leading underscore for private properties? What kind syntax do you have in mind? Today it's just a key=value list. 1 name=string,bge0;class=int,1;media=int,4;phyinst=int,1;phymaj=int,162;devname=string,bge0; Changing file format just for private properties (the use of which we officially discourage) seems like an overkill. -Artem
