Re: MSVC 6.0 or VC++.NET


"sandSpider" <m74.piscean@xxxxxxxxx> wrote in message
news:1120898523.224143.39640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> By the way Os and platorms are upgrading, more and more softwares and
> codes shall require portability issues. I am a C++ developer. Last week
> only I faced a lot of troubles in developing code sticking to the
> basic C++ style and also using MFC.
>
> I have one question.
> Do the newer IDE's and dev env, like VC++.NET provide better support
> for portability issues. I am using MSVC 6. Will I face any portability
> issues and optimizaion issues later.
>
> Maybe should I switch to VC++.NET.
>
> Now, as common sense says, some of the dev's here shall point out that
> it depends on the type of codes I am writing. Well, I think that it
> does not depend on the type of application we are writing , rather
> depends on the way we are writing it. Is the style of coding and
> constructs being used support increase dportability or else is it
> hampering code changes later on.
>
> I want all techies to provide answers, as I am stuck between
> portability, optimization and better code maintenance between using
> MSVC 6.0 and VC++.NET
>
> sandSpiderX
>
Accepting your assertions and ignoring present and future proprietary
extensions, I'd want to switch to the v7.1 C++ compiler (VS .NET 2003)
because it's far more standards-compliant than previous versions.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.


.

Relevant Pages

  • MSVC 6.0 or VC++.NET
    ... codes shall require portability issues. ... I am a C++ developer. ... issues and optimizaion issues later. ... it depends on the type of codes I am writing. ...
    (microsoft.public.vc.mfc)
  • Re: Sizes of Integer Types
    ... Portability is not a black-and-white thing. ... Writing a typedef for an unsigned type that's exactly 32 bits wide ... with no padding bits isn't terribly difficult, ...
    (comp.lang.c)
  • Re: Maximum String size in Java?
    ... >> head was when I was working on unix but writing and testing code at ... I am trying to get certain co-workers to understand the value of writing ... > those that are concerned about portability and those that are not. ... My C pride and joy at the time was a web-based app that pre-dated the ...
    (comp.programming)
  • Re: size_t problems
    ... Writing 100% portable code. ... productivity is low compared to more pragmatic developers, ... Because C was one of the first languages I knew well, ... productivity AND portability through fixed size types. ...
    (comp.lang.c)
  • Re: Telling an empty binary file from a "full" one
    ... left the realms of strict portability. ... If your program is writing files, it's doing so because it needs to communicate something across process boundaries. ... Writing binary data in the native format of your C implementation is probably the narrowest range possible, and only justifiable by laziness. ... Know that it only works if the process on the other side of the boundary is a program compiled by the exact same C implementation, running on the exact same platform. ...
    (comp.lang.c)