<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<blockquote type="cite" cite="mid:2118717224.31682166.1666475526444.JavaMail.zimbra@u-pem.fr">
<div style="font-family: arial, helvetica, sans-serif; font-size:
12pt; color: #000000">
<div data-marker="__QUOTED_TEXT__">
<blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><font size="4"><font face="monospace">What exactly do you mean
by this?</font></font></blockquote>
<div><br>
</div>
<div>If i modify a record by adding a new component, i want to
compiler to help me to find all the switches that are using
that record so i can re-evaulate if the new component play a
role or not for each of those codes.</div>
</div>
</div>
</blockquote>
<br>
What you're asking for is cool, but enormous, because it involves
introducing a new dimension into the programming model -- time.
Currently, we identify which modifications are binary- or source-
compatible, and let people make their choices, but the ways in which
a program has evolved over time is external to the programming
model. <br>
<br>
Adding a component (and doing nothing else) is technically neither a
binary- nor source-compatible change. (Existing constructor
invocations will fail to link.) Of course, you can add a
constructor overload for the old description -- and soon enough,
you'll be able to add a deconstructor overload too. <br>
<br>
<blockquote type="cite" cite="mid:2118717224.31682166.1666475526444.JavaMail.zimbra@u-pem.fr">
<div style="font-family: arial, helvetica, sans-serif; font-size:
12pt; color: #000000">
<div data-marker="__QUOTED_TEXT__">
<div>Then for each code, i can say, i do not care about that
new component by adding an any pattern or i care about it,
add a binding and change/fix the code using that binding.<br data-mce-bogus="1">
</div>
</div>
</div>
</blockquote>
<br>
The plan for dealing with this is the same as with the constructor:
write a deconstructor for the old description. Then all the
existing match sites will continue to work, and you can use "find
usages" to decide which ones you want to migrate. <br>
<br>
<br>
</body>
</html>