In Programers Guide:

CHAPTER 12 MULTI-LANGUAGE PROGRAMMING 293
Overview
TopSpeed has both 16-bit and 32-bit (when released) C++ and Modula-2
compilers that can integrate into the Clarion for Windows environment.
Additionally, 16-bit C and Pascal compilers are also available.The 16-bit
compilers generate object code targeted at traditional Windows
installations
(3.1 and 3.11), while the 32-bit compilers generate object code for the
Windows 95 and Windows NT environments. You must be running your
development environment under a 32-bit environment to generate
applications for a 32-bit environment.

Where this copmilers?

Hello!

Date: 31 Dec 1996 00:31:26 GMT

Alexey Solovjev

But where get this compiler's modules (also C++)?

But where get this compiler's modules (also C++)?

I'd like to know what they mean by "integrate into [] Clarion."

Hello!

Date: 31 Dec 1996 01:46:39 GMT

Alexey Solovjev

I think, what Clarion environment know about this compiler's extension, but
PE 2002 don't have modules (cw2cpp16.dll, cw2m216.dll, cw2pas16.dll).

With the GREAT (!) 32 bit de{*filter*} I found that:
C++32 will set all parameters backwards (this you can work around,
reverse your parameters),
C++32 insert wrong stack instructions when using Win95 API calls
(solution?).
I got a refund without any repons to my reported bugs.
Happy New Year,
Robert Linders

--
+-----------------------------------------------------+
| Robert J. Linders, The Mug Snugglers Corp.          |
| Orlando Florida, ph: 1-888-MugSnug                  |
| fax: 1-407-273-1871                                 |

+-----------------------------------------------------+

#pragma call(c_conv => on | off)
When on, this option enables the Microsoft C calling convention. In this
convention, the compiler pushes function parameters in right to left order
on
the stack and the caller pops these parameters off the stack.

Hello!

Date: 31 Dec 1996 22:44:24 GMT

Alexey Solovjev

Hello!

Date: Wed, 01 Jan 1997 12:22:19 -0500

See a small example:

=== CPP.CLW

   PROGRAM

   MAP
    MODULE('WIN%S%.LIB')
     lstrcpy (*CSTRING,*CSTRING),CSTRING,RAW,PROC,PASCAL,NAME('LSTRCPY')
    END
    MODULE('CPY.CPP')
     cpy (*CSTRING,*CSTRING),CSTRING,RAW,PROC,NAME('_cpy')
    END
   END

Src     CSTRING('Test for 32 bit')
Dest    CSTRING(30)

  CODE
  Dest = '*************'
  lstrcpy (Dest, Src)
  MESSAGE (Dest)

  Dest = '*************'
  cpy (Dest, Src)
  MESSAGE (Dest)

=== CPY.CPP

extern "C" {
  char * pascal lstrcpy (char *, char *);
  char *            cpy (char *, char *);

--
#noedit
#system win32
#model clarion dll
#pragma debug(vid=>min)
#pragma debug(line_num=>on)
#compile cpp.clw
#compile cpy.cpp
#link cpp.exe

=== Dis-assembler of lstrcpy call in CPP.CLW

        PUSH    OFFSET $SRC
        PUSH    OFFSET $DEST
        CALL    LSTRCPY

=== Dis-assembler of lstrcpy call in CPY.CPP

(* Registers settings before _cpy call:
       MOV     eax,OFFSET $DEST
       MOV     ebx,OFFSET $SRC
*)
       PUSH    ebx
       PUSH    eax
       CALL    lstrcpy

=======================

You can run this test and see that it works properly displaying
'Test for 32 bit' instead of asterisks. Also, you can see that
the order of PUSH commands is right-to-left.

Alexey Solovjev

Dear Max,

By the way, using Microsoft 32 bit C++ (version 4.0 or higher) is hardly
an improvement.
MS used the COFF object format and Topspeed/clarion the OMF object
format, and these two just won't mix !!
The CW linker will tell you "unsupported record type 21" when you link
to any object, dll or lib made with the MS compiler.
Shoot, is it so much to ask to interface to a C++ language and keep the
32 bit advantage.
Why is this only a problem to so few people ?

--
+-----------------------------------------------------+
| Robert J. Linders, The Mug Snugglers Corp.          |
| Orlando Florida, ph: 1-888-MugSnug                  |
| fax: 1-407-273-1871                                 |

+-----------------------------------------------------+

Catch you later!

-=> Mike Hanson, BoxSoft <=-

Mike, you want to use a CW DLL or (static) LIB from within C++ ??
I know the linker will try to convert OMF in COFF, but try it with a
small program first, let me know if you are succesfull.

Currently, the CW module is 16-bit, while the C++ stuff is 32-bit.  If
possible, he wants to keep CW in 16-bit, which meant that we are doing
DDE instead (just cold links, with the information passed through a
temporary file).

If I end up changing the CW side to 32-bit, then I'll try the linking
stuff.  If it was just a DLL incompatibility, then I could make the CW
program a LIB (no DLL).  If it's a LIB incompatibility, though, then I
would be stuck.

Catch you later!

-=> Mike Hanson, BoxSoft <=-