Q39261: Don’t Mix .OBJ or .EXE Modules Compiled in Different Versions

Article: Q39261
Product(s): See article
Version(s): 1.00 1.02 2.00 2.01 3.00 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | SR# G881202-7335 B_BasicCom | mspl13_basic
Last Modified: 5-SEP-1990

When you are compiling a series of BASIC programs, Microsoft
recommends compiling all associated routines with the same version
number of the compiler. When the compiler is updated (such as from
version 4.00 to version 4.00b, or version 4.00b to version 4.50), it
is best to re-compile each routine with the new compiler and link with
the new run-time module libraries. Both code generated by the compiler
and the BASIC run-time modules may change between versions.

This information applies to QuickBASIC versions 1.00, 1.02, 2.00,
2.01, 3.00, 4.00, 4.00b, and 4.50; Microsoft BASIC Compiler versions
5.35 and 5.36 for MS-DOS; Microsoft BASIC Compiler 6.00 and 6.00b for
MS-DOS and MS OS/2; and Microsoft BASIC Professional Development
System (PDS) versions 7.00 and 7.10 for MS-DOS and MS OS/2.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.