<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body smarttemplateinserted="true">
<div id="smartTemplate4-template">Hi,<br>
</div>
<div><br>
</div>
<div>there is NewPascal with improved memory safety/smart pointers:
<a class="moz-txt-link-freetext" href="http://newpascal.org/">http://newpascal.org/</a><br>
</div>
<div><br>
</div>
<div><br>
<blockquote type="cite"
cite="mid:e836796e-7f52-d611-8217-34a7c851661d@freepascal.org">but
we try as much as possible to break old code.
</blockquote>
<p><br>
I have noticed that. All my code has been broken by the codepage
aware strings and TEncoding<br>
</p>
<br>
<blockquote type="cite">and FPC's goal to remain
Delphi-compatible.
<br>
</blockquote>
</div>
<div><br>
</div>
<div>So are inline variables coming soon?
<a class="moz-txt-link-freetext" href="http://blog.marcocantu.com/blog/2018-october-inline-variables-delphi.html">http://blog.marcocantu.com/blog/2018-october-inline-variables-delphi.html</a></div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<blockquote type="cite">
Works fine, and I don't think my productivity is in any way
enhanced by all the new features.
<br>
Maybe enumerators save some typing. <br>
</blockquote>
</div>
<div><br>
The new features also generate too often weird assembly, and then
you have to benchmark is the old code faster or the new one, and
then it can turn out the enumerators are slower than an old school
loop , or the case of strings is slower than a hashmap, and then
the new features need to be avoided.<br>
<br>
Best,<br>
Benito </div>
<br>
</body>
</html>