Visual Age C++ to MS VC++ conversion issues?

This is a discussion on Visual Age C++ to MS VC++ conversion issues? within the Windows Programming forums, part of the Platform Specific Boards category; Hi all, I have a set of desktop applications which are running in OS/2 environment to migrate to WinXP environment. ...

  1. #1
    Registered User
    Join Date
    Apr 2002
    Posts
    39

    Question Visual Age C++ to MS VC++ conversion issues?

    Hi all,

    I have a set of desktop applications which are running in OS/2 environment to migrate to WinXP environment.

    A lot of the code is in IBM Visual Age C++. IBM has discontinued the support for it on Windows.

    One option is: convert all this code to MS VC++.

    Other option is: let the code be compiled on NT with an old compiler and take the objects to XP and hope that everything runs (may be with a few alterations).

    My take is that converting to MS VC++ right away is the most sensible thing. But the guy who is going to pay the money feels that it might be easier to just stick with VAC++.

    Anyway, so the question is:

    What could be the potential issues involved in both the options?

    Any inputs would be appreciated.

    TIA.
    <Signature
    name="Ruchikar"
    quote="discussions are forgotten, only code remains"/>

  2. #2
    mustang benny bennyandthejets's Avatar
    Join Date
    Jul 2002
    Posts
    1,401
    If the compiler/language is going out of date, I recommend upgrading to something like Visual C++ .NET. You dont want to have to worry about having support problems on newer systems.
    benforbes@optusnet.com.au
    Microsoft Visual Studio .NET 2003 Enterprise Architect
    Windows XP Pro

    Code Tags
    Programming FAQ
    Tutorials

  3. #3
    Cat
    Cat is offline
    Registered User
    Join Date
    May 2003
    Posts
    1,571
    IF your code is ANSI-compliant C++, you should be OK porting to VC++ .
    Last edited by Cat; 08-07-2003 at 11:43 PM.

  4. #4
    Registered User
    Join Date
    Apr 2002
    Posts
    39
    Problem is not with non ANSI coding.

    Since these are desktop application, a lot of code is screen based visual code. Which uses built-in libraries provided by IBM Visual Age.

    Now that support for VAC++ on windows has been discontinued, such libraries/DLLs are better not used since they too are not supported anymore.

    Converting to MS VC++ means using MFC classes (for instance) instead of VAC++ classes. For which there is no direct mapping (of course). The effort could be large. Or it could be simple, provided there is a conversion strategy about which I don't know.

    If you can put in any inputs, it would be great.

    TIA.
    <Signature
    name="Ruchikar"
    quote="discussions are forgotten, only code remains"/>

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Speed test result
    By audinue in forum C Programming
    Replies: 4
    Last Post: 07-07-2008, 06:18 AM
  2. Forms and MS Visual C++ .NET
    By xddxogm3 in forum C++ Programming
    Replies: 1
    Last Post: 05-24-2007, 06:50 PM
  3. Difference in MSVC 6 & MS VC .Net
    By passionate_guy in forum C Programming
    Replies: 1
    Last Post: 01-23-2006, 06:39 AM
  4. Please Help - Problem with Compilers
    By toonlover in forum C++ Programming
    Replies: 5
    Last Post: 07-23-2005, 11:03 AM
  5. <list>
    By Unregistered in forum C++ Programming
    Replies: 9
    Last Post: 02-24-2002, 04:07 PM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21