In our previous episode, Sven Barth said:
This was my first guess as well, but deactivating online-scanning didn't
help. So I uninstalled BitDefender completely, and now it worked :-)
It's fascinating how much can be broken by an anti virus program -.-
If you want the full experience, I
Am 28.11.2011 um 01:05 schrieb Jonas Maebe:
On 28 Nov 2011, at 00:49, Michael Müller wrote:
Beside that what is than the difference between 'out' and 'var'?
If you enable hints, the compiler will print a hint if it detects you passing
a potentially uninitialized variable to a var
Am 28.11.2011 12:02, schrieb Michael Müller:
Additionally, if you use the -gt command line option then the compiler will overwrite the
contents of (non-reference-counted) out-parameters in the function entry code. This
switch will do nothing for open array parameters though, because it lacks
On 28 Nov 2011, at 12:02, Michael Müller wrote:
Am 28.11.2011 um 01:05 schrieb Jonas Maebe:
If you enable hints, the compiler will print a hint if it detects
you passing a potentially uninitialized variable to a var
parameter, while it won't print such a warning if you pass it to an
out
28.11.2011 14:26, Sven Barth пишет:
Am 28.11.2011 12:02, schrieb Michael Müller:
Additionally, if you use the -gt command line option then the compiler will
overwrite the
contents of (non-reference-counted) out-parameters in the function entry code.
This switch will
do nothing for open array
14.11.2011 7:02, Alexander Shishkin пишет:
Currently assigning UnicodeString to variant converts string to
WideString and makes variant of type varOleStr.
I think it should be varUString and w|o any conversion (also this is
delphi compatible). But the question is which type should be if
I just implemented and option to create an XML project from the
commandline arguments. This should allow to create projects from the
scripts and Makefiles, used to build the documentation for the standard
libraries. See Mantis #20769.
Unfortunately there remain some problems, e.g. the FPC
