<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><blockquote type="cite" id="qt" style=""><div style="font-family:sans-serif;"><div style="white-space:normal;"><p dir="auto">ASDF checks to make sure all of the initargs are defined when parsing a <code style="background-color:rgb(247, 247, 247);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0.4em;padding-bottom:0px;padding-left:0.4em;" bgcolor="#F7F7F7">defsystem</code>. This is good for catching errors, but is terrible for extensibility. This means that any attempt to add additional metadata will be backwards incompatible.<br></p><p dir="auto">I can think of two ways to fix this:<br></p><ol><li value="1"><p dir="auto">Add a "garbage can" slot to <code style="background-color:rgb(247, 247, 247);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0.4em;padding-bottom:0px;padding-left:0.4em;" bgcolor="#F7F7F7">component</code> that will be filled with a property list, and allow programmers to do whatever they want here. This doesn't seem great to me.<br></p></li><li value="2"><p dir="auto">Add a new <code style="background-color:rgb(247, 247, 247);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0.4em;padding-bottom:0px;padding-left:0.4em;" bgcolor="#F7F7F7">defsystem</code> parsing error class that is <code style="background-color:rgb(247, 247, 247);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0.4em;padding-bottom:0px;padding-left:0.4em;" bgcolor="#F7F7F7">unknown-component-property</code>, raise it when an unknown property is encountered and allow the user to continue, discarding the initarg and accompanying value.<br></p></li></ol><p dir="auto">The second alternative is what I favor. It isn't great, because it will only maintain extensibility going forward, but I think it's the best we can do.<br></p></div></div></blockquote><div><br></div><div>How can ASDF or a developer determine that the unknown property doesn't change the semantics of the DEFSYSTEM, and therefore discarding it would have an effect that's contrary to the author's intention ?<br></div><div>ASDF has no syntactic distinction between properties that affect the compilation process and mere annotations like author, licence, etc...<br></div><div><br></div><div><br></div><blockquote type="cite" id="qt" style=""><div style="font-family:sans-serif;"><div style="white-space:normal;"><p dir="auto">I suppose that we could also add an initarg to tell ASDF to continue such errors silently.<br></p><div dir="auto"> I'd be inclined to suggest that this take an ASDF version expression as value, so that the error is quietly ignored only by ASDF versions below that. This means that the property will start to be checked when it has become authoritative.<br></div><p dir="auto">Note that for one's own <code style="background-color:rgb(247, 247, 247);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0.4em;padding-bottom:0px;padding-left:0.4em;" bgcolor="#F7F7F7">system</code> and <code style="background-color:rgb(247, 247, 247);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0.4em;padding-bottom:0px;padding-left:0.4em;" bgcolor="#F7F7F7">component</code> subclasses, the set of initargs can be extended without any monkeying around.<br></p></div></div></blockquote><div><br></div><div><br></div><div><span style="color:rgb(0, 0, 0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;orphans:2;text-align:start;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;-webkit-text-stroke-width:0px;background-color:rgb(255, 255, 255);text-decoration-thickness:initial;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline !important;"><span class="font" style="font-family:system-ui, -apple-system, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Fira Sans", "Droid Sans", "Helvetica Neue", Arial, sans-serif;"><span class="size" style="font-size:13.125px;">This is a recipe for maintenance nightmares. Let's not go there.</span></span></span><br></div><div><br></div><div id="sig4916231"><div class="signature">--<br></div><div class="signature">Stelian Ionescu<br></div></div><div><br></div></body></html>