Python + Borland - msvcrt = grr.

[Stephen Hansen]

"Neil Hodgson" <nhodgson at bigpond.net.au> wrote in message
>    BCC tries hard to find never used value settings, including some that
> other compilers don't warn about. For example, IIRC, this generates a
> warning because the 1 is never read:
>    int i = 1;
>    if (c)
>       i = 2;
>    else
>       i = 3;
>    As does the same thing in a switch statement. BCC may also sometimes
work
> out when loops will never be run or be run only once. I can't recall all
the
> cases but BCC has always been accurate when its given me this warning.

    That's the reply I just received from the borland.* newsgroups. That
just strikes me as *weird*. It explains the infinate spam of warning
messages I get, though, since quite a few pointers are initialized to NULL
and that NULL is never read in. This is not something I think the
Gods'o'Python would care to have fixed, though. Dispite a 'no warnings'
policy :)

--S
(replace 'NOSPAM' with 'seraph' to respond in email)