<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Hi Eirik,<br>
<br>
The lack of `Boolean.getBoolean(String propName, boolean default)`
encourages<br>
developers to roll their own. If it were easier get the desired
default from the built-in<br>
boolean property API it would fit more use cases.<br>
<br>
It might be a small step to take advantage of your analysis and be a
useful addition to the API.<br>
<br>
There is usually less engagement during the later half of December,
so it might be a while before any support is evident.<br>
<br>
$.02, Roger<br>
<br>
<br>
<div class="moz-cite-prefix">On 12/4/24 12:57 PM, Eirik Bjørsnøs
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CA+pBWhsc943THfpppc7WnD-6ZJwVybm1-OWVBJ0MVxbGnr-EQg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div>There are at least three issues at play here: </div>
<div><br>
</div>
<div>a: Some flags use inconsistent, confusing,
controversial or less-than-perfect interpretations</div>
<div>b: Some flags use identical interpretations, yet
their evaluation happens in copy-pasted code spread
across the code base</div>
<div>c: Some flags use identical interpretations, yet
the code written to evaluate that interpretation
varies a lot across the code base</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Let me add:</div>
<div>d: Maintainers introducing new flags lack guidance for
picking a "good" flag interpretation</div>
<div>e: Maintainers introducing new flags must write new code
to read the property value and reduce the following to a
boolean: [null | empty | "true" | "TRUE" | "false" | "FALSE"
| "unrelated"]</div>
<div><br>
</div>
<div>Eirik.</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>