Re: Division inconsistent between Debug/Release builds

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: John C. Kirk (jkirk_at_pmsi-consulting.com)
Date: 01/05/05


Date: Wed, 5 Jan 2005 14:19:10 -0000


> In addition to Mattias' suggestion on understanding what might be going
> on...
> I would also recommend explicitly defining what you want it to do.

Thanks to both of you for the advice on that. I've found a workaround, so
that aspect isn't a major problem, it's more the different behaviour that
was bothering me.

> As far as the difference between modes, this is entirely possible.
> You have various amounts of precision available. I am not certain what
> exactly is going on in each scenario, but it does not surprise me they are
> different. This is common, even expected, behaviour when dealing with
> floating point variables.

I know that Debug and Release modes actually generate different MSIL, so I
can accept them giving different results (although it's annoying). But is
there any advantage at all to running in Release mode inside the IDE? It
doesn't help you for testing, since you won't necessarily get the same
results as end users. And it won't help you to isolate errors, since you
can't break into the source code. The only advantage I can see is that it's
easier to click the "run" toolbar button than to browse for the file in
Explorer and double-click on it there, but surely that's just a question of
how the toolbar button code is implemented?

John



Relevant Pages

  • Re: How do I approach this?
    ... software before you have an understanding about ownership. ... their time you further complicate the situation. ... >>> recently regarding the source code. ...
    (microsoft.public.vstudio.development)
  • Re: How to read log files
    ... kernel log, messages, dmesg, and such? ... I have been googling but found ... there is always the source code *horror*. ... Understanding log files is - while not art - sometimes hard labor. ...
    (Debian-User)
  • Re: Defendant wins breathalyzer source code
    ... controlling the breathalyzer and the source code is what was used to ... The justification is they are aids to understanding. ... The other point is the defence would ask for them and if you argue, prevaricate or equivocate the defence and jury would "know" you had something to hide. ...
    (comp.arch.embedded)
  • RE: White line (1px) between mainmenu and toolbar controls
    ... Based on my understanding, you want to get rid of the 1px white line ... between ToolBar and MainMenu. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: How safe is intellectual property in compiled binaries?
    ... Will people be able to disassemble/decompile your code to view the source code? ... At this point, you've probably spent some time working with other people's programs, and thus you should be aware that for a large computer program, understanding it _with_ the benefit of the proper source code and comments and so forth can take months. ... I will probably speak to my supervisors when my thesis submission date is closer, but I'm interested to hear from the PhD holders here -- whether you think it is a good idea to "dumb down" the program you submit with your thesis, so that you alone remain the only person who can do this-or-that. ... Beyond that, I owe a debt to other authors who put their algorithms out in public -- their publications saved me months of work in getting results, and notably improved the results that I did get. ...
    (comp.lang.fortran)