<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Il 30/06/23 19:40, Mattias Gaertner via
lazarus ha scritto:<br>
</div>
<blockquote type="cite"
cite="mid:20230630194037.34b71bc8@limapholos">
<pre class="moz-quote-pre" wrap="">Michael Van Canneyt via lazarus <a class="moz-txt-link-rfc2396E" href="mailto:lazarus@lists.lazarus-ide.org" moz-do-not-send="true"><lazarus@lists.lazarus-ide.org></a> wrote:
</pre>
<blockquote type="cite" style="color: #007cff;">
<pre class="moz-quote-pre" wrap="">[...]
Honestly: I'll settle for actually managing to get a release out.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">+1000</pre>
</blockquote>
<p>+1000 me too.<br>
</p>
<p><RANT><br>
</p>
<p>If the brilliant minds which have elaborated a new numbering
scheme had spent their time in something more productive, such as
making life a little bit easier to developers, I believe that the
Lazarus community would have appreciated much more!</p>
<p>For instance, there is the bad habit to "deprecate" without
considering what happens to developers which must maintain their
programs. I found it rather frustrating to replace all occurrences
of clDark with clDkGray, just because clDark had been deprecated,
instead of simply replacing the definition wit a line in types
clDark = clDkGray.</p>
<p>I've been taught that the golden rule to make code reusable is to
hide the implementation and expose only the feature. Who cares how
a color is implemented, provided that it shows the same? The same
holds true for a lot of deprecations, which could be easily hidden
without any adverse effect.</p>
<p></RANT></p>
<p>Giuliano<br>
</p>
<pre class="moz-signature" cols="72">--
Do not do to others as you would have them do to you.They might have different tastes.</pre>
</body>
</html>