> On Oct 4, 2018, at 9:19 PM, Michael Van Canneyt
> wrote:
>
> And was this not the whole idea of introducing a default property in the
> first place ?
It is but I just wanted to make sure that this particular ambiguity with
initializing classes wasn’t concerning for anyone.
So far I’ve
On Thu, 4 Oct 2018, Ryan Joseph wrote:
On Oct 4, 2018, at 8:34 PM, Michael Van Canneyt wrote:
Technical issues aside, it kind of defeats the purpose of the default
property...
Then just tolerate the fact we have a dual meaning for assignments? Looks wrong
but maybe not a problem.
var
> On Oct 4, 2018, at 8:34 PM, Michael Van Canneyt
> wrote:
>
> Technical issues aside, it kind of defeats the purpose of the default
> property...
Then just tolerate the fact we have a dual meaning for assignments? Looks wrong
but maybe not a problem.
var
wrapper: TWrapper;
begin
On Thu, Oct 4, 2018 at 4:02 AM wrote:
> This is one of the most useless collection of floating point myths I
> have seen since a long time.
>
> With rolling a dice you mean, that the comparisons are only
> randomly correct or what)? Since the floating-point numbers
> are well-defined and exact
On Thu, 4 Oct 2018, Ryan Joseph wrote:
On Sep 26, 2018, at 1:14 AM, Benito van der Zander wrote:
Hi,
perhaps everything would be clearer, if the default property was accessed with ^ ?
var
wrapper: TWrapper;
begin
wrapper := TWrapper.Create;
wrapper^ :=
> On Sep 26, 2018, at 1:14 AM, Benito van der Zander wrote:
>
> Hi,
>
> perhaps everything would be clearer, if the default property was accessed
> with ^ ?
>
>
> var
> wrapper: TWrapper;
> begin
> wrapper := TWrapper.Create;
> wrapper^ := THelperA.Create;
> end.
>
This is one of the most useless collection of floating point myths I
have seen since a long time.
I don't know why you want to compare two floats, but you'd better
use currency type. Float is for calculus, but comparing
float1=float2 (or float1>float2) is rolling the dice. Obviously, the
