Re: Linking DLL's across different compilers and languages

32-bit 2's complement values are 32-bit 2's complement values. "Signed" and "unsigned"
are artificial concepts we impose on these values. Whether or not these have meaning is
very dependent on the problem domain and expectations of the code, so passing around
32-bit values is perfectly safe, providing you don't expect to compare absolute magnitudes
of these values in VB. For example, if you expect all values to be < 0xFFFFFFF then your
code is not going to work particularly well. But you can certainly pass the values around
without hindrance.
joe

On Sun, 3 Dec 2006 07:10:39 -0600, "Peter Olcott" <NoSpam@xxxxxxxxxxxxx> wrote:


"Ajay Kalra" <ajaykalra@xxxxxxxxx> wrote in message
news:1165123224.626265.322990@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
To what extent can a DLL created with MS Visual C++ be used across different
compiler versions, different compiler vendors, and different computer
languages
be used? Some of the data provided by one of the functions will be unsigned
int,
is there any way to make this work with VB?

A DLL of a specific type is simply a DLL regardless of compiler vendor
or computer languages. These factors have no bearing on the DLL itself.

Not knowing much about VB, it however does allow you to access Win32
DLLs. It will also be able to access MFC Regular DLLs. Any method
exported in these DLLs can be accessed in VB using GetProcAddress. VB
also allows easy access to COM servers, which is its one of its main
selling points.

---
Ajay

What about VB's inability to handle unsigned integer types? Is there any way
around this that you can conceive?

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: Linking DLLs across different compilers and languages
    ... compiler versions, different compiler vendors, and different computer languages ... Some of the data provided by one of the functions will be unsigned int, ... A DLL of a specific type is simply a DLL regardless of compiler vendor ...
    (microsoft.public.vc.mfc)
  • Re: Linking DLLs across different compilers and languages
    ... For equality, 32-bit values are equal to 32-bit values, ... instead of an unsigned int. ... compiler versions, different compiler vendors, and different computer ... A DLL of a specific type is simply a DLL regardless of compiler vendor ...
    (microsoft.public.vc.mfc)
  • Re: Linking DLLs across different compilers and languages
    ... For equality, 32-bit values are equal to 32-bit values, and signedness ... instead of an unsigned int. ... compiler versions, different compiler vendors, and different computer ... A DLL of a specific type is simply a DLL regardless of compiler vendor ...
    (microsoft.public.vc.mfc)
  • Re: Linking DLLs across different compilers and languages
    ... compiler versions, different compiler vendors, and different computer ... A DLL of a specific type is simply a DLL regardless of compiler vendor ... or computer languages. ... What about VB's inability to handle unsigned integer types? ...
    (microsoft.public.vc.mfc)
  • Re: Linking DLLs across different compilers and languages
    ... instead of an unsigned int. ... compiler versions, different compiler vendors, and different computer ... A DLL of a specific type is simply a DLL regardless of compiler vendor ... What about VB's inability to handle unsigned integer types? ...
    (microsoft.public.vc.mfc)
Loading