Re: Porting a win32 application from vc++ to VS 2005 .NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Oriane wrote:
"Victor Bazarov" <v.Abazarov@xxxxxxxxxxxx> a écrit dans le message de
news: edp9oa$hgg$1@xxxxxxxxxxxxxxxxxx
Oriane wrote:
I'm currently trying to update an old app from VC++ 6.0 to Visual
Studio .NET 2005. I've let the wizard make the "makefile"
translation, and now it is compiling and linking but the executable
file is not the same size...

Is there a tool or an URL which could help me ? How can I track the
discrepancies between the compilatoin options ?

But you're already using the tool! It's called "the compiler".

Porting from one version of a compiler to another almost never has
any specifics. Compile, run, see if it behaves the same way, then
you're done. Deal with errors on each step. If it doesn't compile,
fix it. If it compiles but the behaviour is different, fix it.

The executable size is immaterial. Of course it's different, you're
using a different compiler now.

V
So is the empirical method the good one ? I'm a bit disappointed...

Empirical? Not sure what you mean. Supposedly, your program contains
all the code necessary to verify its proper behaviour. If not, you are
supposed to have an automated set of test cases (a test suite) that will
tell you if something is wrong. By utilising one or the other (ot both)
you should be able to see if the behaviour of the next version is the
same as the previous one. Nothing empirical about it. I would probably
use the term "methodical".

And what are you disappointed about? If you write your program to rely
on some features specific to a particular compiler, you have a problem
of "porting". If you just write your program using the language and
OS API, without "tuning" it to any compiler, "porting" doesn't really
exist, or, it's rather a problem for the compiler writers. A working
program should remain working. If it doesn't, then you need to research
the cause and deal with it. And that's called "development". No tool
is going to replace *you* in that process.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask


.

Relevant Pages

  • Some fixes for ZFS on 7-stable (more testers wanted)
    ... pjd - applicable to RELENG_7? ... Fix locking. ... NOT APPLICABLE to ZFS in 7-stable ... However, on ia64, the compiler is quite agressive in finding ILP ...
    (freebsd-stable)
  • Re: STM32 ARM toolset advice?
    ... Compulsory car comparison: would you buy a car where the motor block is ... you yourself using a self-help book) can fix? ... compilers work better than a compiler vendor. ...
    (comp.arch.embedded)
  • Re: How many bytes per Italian character?
    ... There's a reason I don't use free open-source products: ... someone once said "Well, you should use gcc because that way, if you find a bug ... I used to work for a compiler company. ... *know* how hard it is to fix bugs in optimizing compilers. ...
    (microsoft.public.vc.mfc)
  • Re: "no variable or argument declarations are necessary."
    ... > say I write some Python code, using assert to validate datatypes. ... I fix the first error, ... I can often run 4 Python edit-debug cycles in the time it takes me to ... I'll spend more time making the compiler happy than the ...
    (comp.lang.python)
  • Re: size_t problems
    ... You really should bite the bullet and fix the code. ... Believe me, I know what porting means, what is important in code ... software package supplied by the vender is *full* of pre C89 crud. ... The compiler would yell at me. ...
    (comp.lang.c)