Re: Using Borland C++ object files in VC++
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Fri, 2 Mar 2007 14:12:16 -0500
Jochen Kalmbach [MVP] <nospam-Jochen.Kalmbach@xxxxxxxxx> wrote:
If the declaration of the function is correct there should be no
problems...
for example:
int calc(int a, int b);
should work as 16 and 32 bit...
Should it? 32-bit caller would push 64 bit worth of data on the stack.
16-bit callee would only pull 32 bit worth of data. The callee would put
return value into AX register, leaving the high word of EAX unmodified.
How again is this supposed to work?
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: Using Borland C++ object files in VC++
- From: Jochen Kalmbach [MVP]
- Re: Using Borland C++ object files in VC++
- References:
- Using Borland C++ object files in VC++
- From: gokcen
- Re: Using Borland C++ object files in VC++
- From: gokcen
- Re: Using Borland C++ object files in VC++
- From: Jochen Kalmbach [MVP]
- Re: Using Borland C++ object files in VC++
- From: Alex Blekhman
- Re: Using Borland C++ object files in VC++
- From: Jochen Kalmbach [MVP]
- Using Borland C++ object files in VC++
- Prev by Date: Re: Using Borland C++ object files in VC++
- Next by Date: Re: memory not released by delete[] operator
- Previous by thread: Re: Using Borland C++ object files in VC++
- Next by thread: Re: Using Borland C++ object files in VC++
- Index(es):
Relevant Pages
|