> More broadly I think the bigger problem is FPC's internal over-eagerness to > implicitly cast things to other things... for example, if you have a type with > an ":=" operator overload (or as Delphi calls it, an "Implicit" operator > overload) from both "Pointer" and "TObject", FPC will always pick the > "Pointer" > one even if given an explicit TObject variable. They (currently) cannot > co-exist. But certainly, they should be able to, if you ask me.
I still find "nil->Pointer->dynarray->UCS4String" the most hilarious "weight 1" autoconversion (see 0031215, which is also an overload bug). -- Regards, Martok _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
