On Sun, Nov 21, 2010 at 9:22 PM, Michael Van Canneyt wrote:
>
>
> On Sun, 21 Nov 2010, Max Vlasov wrote:
>
> Hi,
>> I'm one of those developers who takes hints and warnings seriously and I
>> must say at least once a week it helps me find a bugs even before running
>> the
>> program. So when I g
On Sun, 21 Nov 2010, Max Vlasov wrote:
Hi,
I'm one of those developers who takes hints and warnings seriously and I must
say at least once a week it helps me find a bugs even before running the
program. So when I got a warning about some uninitialized variable passed by
reference (Delphi 5 i
On Sun, Nov 21, 2010 at 6:37 PM, Sven Barth wrote:
> On 21.11.2010 16:22, Max Vlasov wrote:
>
>> But is it possible to do the same (partially, gradually or in any other
>> way) for the "legacy" code that keeps the interface compatibility with
>> Delphi. For example TStrignList.Find(const S: string
On 21.11.2010 16:22, Max Vlasov wrote:
Hi,
I'm one of those developers who takes hints and warnings seriously and I
must say at least once a week it helps me find a bugs even before
running the program. So when I got a warning about some uninitialized
variable passed by reference (Delphi 5 is ok
Hi,
I'm one of those developers who takes hints and warnings seriously and I
must say at least once a week it helps me find a bugs even before running
the program. So when I got a warning about some uninitialized variable
passed by reference (Delphi 5 is ok with such variable being uninitialized),