[krbdev.mit.edu #9120] [Comment] profile final flag limitations
"Greg Hudson via RT" <[email protected]> Sun, 14 Apr 2024 10:24:41 -0400
| Newsgroups | gmane.comp.encryption.kerberos.bugs |
|---|---|
| Message-ID | <rt-4.4.3-2-1759841-1713104681-1798.9120-8-0@kerborg-prod-app-1.mit.edu> |
http://kerborg-prod-app-1.mit.edu/rt/Ticket/Display.html?id=9120 This is a comment. It is not sent to the Requestor(s): Another note: whlie the syntax and data model can naturally accommodate an empty section or subsection with the final flag set, neither can naturally represent a final-flagged relation with no values. (In the memory representation, a node with the deleted and final flags set could possibly do in a pinch, but it isn't a natural representation. A node with a null value is semantically a section, not a relation.) So, even with the two numbered limitations above addressed, there is no way to use the final flag to force the use of the default value for a variable, or to force an empty list for a relation that can have multiple values.