On 10/13/2014 04:14 PM, hinsta...@yandex.ru wrote:
Maybe; however I am asking about reference counted objects feature.
Sorry for the fuzz. (Your contribution was a direct reply to my mail
about parallel loops.)
-Michael
___
fpc-devel maillist -
On 10/13/2014 04:14 PM, hinsta...@yandex.ru wrote:
I thought Svan Barth said that he considered implementing it
Regarding this, Maybe, Success in implementing should be preceded by a
decision if and how this feature does make sense regarding the possible
addition danger it offers (see the
Am 14.10.2014 09:09 schrieb Michael Schnell mschn...@lumino.de:
On 10/13/2014 04:14 PM, hinsta...@yandex.ru wrote:
I thought Svan Barth said that he considered implementing it
Regarding this, Maybe, Success in implementing should be preceded by a
decision if and how this feature does make
On 10/14/2014 11:50 AM, Sven Barth wrote:
It's a proof of concept implementation to have real code to work with
instead of just theories. Also it's in a separate branch, so it
doesn't interrupt any existing code except one explicitly uses that
branch.
Sounds good.
-Michael (curious...)
Hello!
My original task is to make GZIP stream compression/decompression
(preferably without external libraries).
I read zlib specification in http://www.zlib.net/manual.html and tried
to use WindowBits = 16 for automatic GZIP wrapping, but in FPC it does
not works too (in Delphi XE2 works fine).
Am 14.10.2014 12:41 schrieb Marco van de Voort mar...@stack.nl:
I recently had to dive a bit into C++ again, and reconnected with a
feature
I liked at first sight, the C++ covariance of virtual methods (changing
the
return type of a overriden method to a descendant of the original type).
In our previous episode, Sven Barth said:
At least at first sight there don't seem to be any real (technical) reasons
to not covariance for return values. Parameters would be a different topic
though...
Specially since afaik we can't overload on returnvalue and require override,
so there is no
On 14 Oct 2014, at 14:21, Sven Barth wrote:
At least at first sight there don't seem to be any real (technical)
reasons
to not covariance for return values.
Delphi and/or FPC already support it to a certain extent, and the
compiler contains some code for it (see
On Tue, Oct 14, 2014 at 7:40 AM, Marco van de Voort mar...@stack.nl wrote:
I recently had to dive a bit into C++ again, and reconnected with a feature
I liked at first sight, the C++ covariance of virtual methods (changing the
return type of a overriden method to a descendant of the original
Sven Barth schrieb:
At least at first sight there don't seem to be any real (technical)
reasons to not covariance for return values. Parameters would be a
different topic though...
Just so I get the idea right:
=== code begin ===
type
TBar = class
function Test: TObject; virtual;
On 14.10.2014 15:34, Jonas Maebe wrote:
On 14 Oct 2014, at 14:21, Sven Barth wrote:
At least at first sight there don't seem to be any real (technical)
reasons
to not covariance for return values.
Delphi and/or FPC already support it to a certain extent, and the
compiler contains some code
On 15.10.2014 04:21, Hans-Peter Diettrich wrote:
Sven Barth schrieb:
At least at first sight there don't seem to be any real (technical)
reasons to not covariance for return values. Parameters would be a
different topic though...
Just so I get the idea right:
=== code begin ===
type
TBar
12 matches
Mail list logo
