<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 20.12.2015 17:51, Jürgen Hestermann
wrote:<br>
</div>
<blockquote cite="mid:5676DC89.30603@gmx.de" type="cite">>
Writing a documentation for features in development is not very
reasonable.
<br>
<br>
Realy?
<br>
I thought that it is very important to document the <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>intended<span
class="moz-txt-tag">*</span></b>
<br>
behaviour somewhere before (or at least while) coding it
<br>
so that everybody knows how things <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>should<span class="moz-txt-tag">*</span></b>
work and
<br>
can distinguish bugs from features.
<br>
Without documentation every bug becomes an intended behaviour.
<br>
</blockquote>
<br>
Yes, that's true. But you have to understand that a scope of some
days between bug fixing and documenting should be tolerable.<br>
<br>
<br>
<div class="moz-cite-prefix">On 20.12.2015 17:51, Jürgen Hestermann
wrote:<br>
</div>
<blockquote cite="mid:5676DC89.30603@gmx.de" type="cite">> Always
look for documentation in trunk or the fixes branch. <br>
<br>
Where do I find it? <br>
I use official (pre) releases only. <br>
</blockquote>
<br>
You find the documentation if you keep your mouse on the identifier
in the source code in the official (pre) releases. <a
class="moz-txt-link-freetext"
href="http://lazarus-ccr.sourceforge.net/docs/lcl/dialogs/questiondlg.html"><a class="moz-txt-link-freetext" href="http://lazarus-ccr.sourceforge.net/docs/lcl/dialogs/questiondlg.html">http://lazarus-ccr.sourceforge.net/docs/lcl/dialogs/questiondlg.html</a></a>
is generated from the same source.<br>
<br>
<br>
<div class="moz-cite-prefix">On 20.12.2015 17:51, Jürgen Hestermann
wrote:<br>
</div>
<blockquote cite="mid:5676DC89.30603@gmx.de" type="cite">> It is
told to be updated with new stable versions so now it should
reflect 1.4. <br>
> Of course you don't find the latest features there. <br>
<br>
Okay, so the main reason for my problems is that I did not wait
until the <br>
official release of Lazarus 1.6. I thought that RC1 should already
be stable <br>
</blockquote>
<br>
RCs are not stable :(<br>
<br>
<br>
<blockquote cite="mid:5676DC89.30603@gmx.de" type="cite">
and wanted to help with testing (expecting only minor bugs only).
<br>
But it seems that was not a good idea. <br>
</blockquote>
<br>
On the contrary! It was a great idea and you pointed us/me to the
fact that there is information missing. Please test RCs in the
future as well. Thanks to you, it will be fixed for the 1.6 stable.<br>
<br>
<br>
<div class="moz-cite-prefix">On 20.12.2015 17:51, Jürgen Hestermann
wrote:<br>
</div>
<blockquote cite="mid:5676DC89.30603@gmx.de" type="cite">> As
latest, you have the source code, so you can check it as well -
that usually is better than any documentation. <br>
<br>
You cannot mean this seriously, do you? <br>
You mean I should wade through <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>all<span class="moz-txt-tag">*</span></b>
the <br>
lines of code and understand each and every <br>
line to discover new features and how they work? <br>
</blockquote>
<br>
Yes, I mean this seriously. You don't have to go through all the
code, just the code that doesn't work as you expect. I do the same -
if there is something I don't understand or it behaves differently
from the docs, I look into the code and check why.<br>
<br>
Ondrej<br>
<br>
</body>
</html>