<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 02/28/2017 08:58 PM, David Blaikie
wrote:<br>
</div>
<blockquote
cite="mid:CAENS6EviVP8qnn5BzhDPKJC67siQs7=GdStbrqUJsxnVZbKWKQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr"><br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Tue, Feb 28, 2017 at 9:55 AM Victor Leschuk
<<a moz-do-not-send="true"
href="mailto:vleschuk@accesssoftek.com">vleschuk@accesssoftek.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<p class="gmail_msg">Maybe we should just add one more
constructor for DWARFFormValue which would set both Form
and Value fields?</p>
</div>
</blockquote>
<div>That's /sort/ of what I'm suggesting, but providing a
wrapper around that data so the code here doesn't have to
have explicit support for values. It should be part of some
'form' abstraction/concept (that carries both the form
enumerator and any other data is needed - the value).</div>
</div>
</div>
</blockquote>
I understand, but isn't DWARFFormValue already such a wrapper
itself? It holds enumerator and a union field which hides the actual
data representation. We just need to widen it's API in order to be
able construct it with one call, not construct+initialize.<br>
</body>
</html>