sarif — archive

RE: [sarif] #401: Improved design of address object design

From: Laurence Golding
To: [email protected]
Date: Mon, 29 Apr 2019 18:46:00 -0000

I m not as happy as I was a few moments ago. If the unknown properties default to false , then if you don t populate offsetFromParent (which happens at the top of every parent chain) or length (which can happen anywhere along the parent chain), then you have to remember to set the corresponding unknown property. You won t. Of if the unknown properties default to true , you have to set them to false whenever you do populate offsetFromParent or length . You won t. Michael (addressing this question specifically to him because of the SDK impact), I don t see a good alternative to Nullable<int> . Please let us know your opinion. Raising to red-bang. Larry From: Larry Golding (Myriad Consulting Inc) Sent: Monday, April 29, 2019 11:37 AM To: James Kupsch <[email protected]>; Michael Fanning <[email protected]>; OASIS SARIF TC Discussion List <[email protected]> Subject: RE: [sarif] #401: Improved design of address object design I could accept Boolean unknownLength and unknownOffsetFromParent, default false for both. I will write it this way and send a draft. I can always change this aspect of the design if the TC objects. Larry