KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q27475: Can’t Pass QuickBASIC COMMON Block to FORTRAN

Article: Q27475
Product(s): See article
Version(s): 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | B_BasicCom | mspl13_basic
Last Modified: 14-JUN-1989

When passing a FORTRAN COMMON block to a compiled BASIC procedure, the
first variable in the FORTRAN COMMON block is passed as a parameter in
the CALL statement. The compiled BASIC procedure receives the variable
as a user-defined type that corresponds to the COMMON block. This
works when passing a FORTRAN COMMON block to a compiled BASIC
procedure, but is not supported for passing a BASIC COMMON block to a
FORTRAN routine, because FORTRAN does not support user-defined types.

You cannot pass a COMMON block defined in a compiled BASIC procedure
to a FORTRAN routine.

This information applies to Microsoft QuickBASIC Versions 4.00, 4.00b,
and 4.50 for MS-DOS, and to the Microsoft BASIC Compiler Versions 6.00
and 6.00b for MS-DOS and 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.