Re: problem with output of the program on different OS

In article
<3fc750e9-705e-43f3-a5c8-20734357480c@[EMAIL PROTECTED]
>,
Bart  <bc@[EMAIL PROTECTED]
> wrote:
>On May 10, 1:24 pm, Richard Heathfield <r...@[EMAIL PROTECTED]
> wrote:

>> I haven't got as far as executing it yet. When I get some more time,
I'll
>> do some more code clean-up. When eventually I get around to executing
it,
>> I'll post the result here.
>
>Is it some principle of yours that you never execute any code until
>every possible warning has been eliminated and it has been styled
>entirely to your satisfaction?
>
>Sounds a bit like premature optimisation to me (when you eventually
>run it you find you have to change all that beautifully crafted code).

I can't speak for RH, but I never execute code until I have at least
reasonable confidence that it will do something not entirely unlike
what I expect.  The sooner you find and fix errors, the easier it is,
and it's hard to catch coding errors much sooner than "before you run
the code" (though design errors can often be caught before you even
start writing the code).

Eliminating compiler warnings and, for many (but far from all)
stylistic preferences, modifying code to conform to those stylistic
preferences is one way (and a rather cost-effective one when done well)
to increase the level of confidence that the code will do something not
entirely unlike what the programmer expects.


dave

-- 
Dave Vandervies                              dj3vande at eskimo dot com
Oh I don't know. There's probably some decent land within a mile or so.
(Shame about all that water you have to dive through to reach it.)
                                  --Tanuki in the scary devil monastery