Visual Basic, visual basic 4.0 call to borland c++ 5.0 dll

visual basic 4.0 call to borland c++ 5.0 dll

Author	Message
Ron Rubl #1 / 4	visual basic 4.0 call to borland c++ 5.0 dll Should be identical to the rules for VC++; in fact, you have one advantage in that I believe Borland Doesn't mangle names exported with stdcall. File naming is not a problem. The details should be in a file similar to VB4DLL.TXT (in VB 5, All the details are in the file VB5DLL.DOC on the VB5 CD in the VB5.0\TOOLS\DOCS folder). -- Ron Ruble Raffles Software Development, Inc. Quote: >Hello, >I have seen many references to this problem but I need help for my >specific situation. I have been sifting through reams of documentation >dealing with the declaration and calling of dynamic link libraries but >I have yet to find exactly what I need. My problem: I need to find the >correct syntax for declaring and referencing a Borland C++ 5.0 >dynamic link library (that also needs to be created, so I need the correct >file naming convention as well as the way to correctly declare >individual subroutines within the dll) from within a Visual Basic 4.0 >application. Can anybody help me. >Chuck
Thu, 13 Jul 2000 03:00:00 GMT

Chris Marriot #2 / 4	visual basic 4.0 call to borland c++ 5.0 dll Quote: >Should be identical to the rules for VC++; in fact, >you have one advantage in that I believe Borland > Doesn't mangle names exported with stdcall. The Microsoft compiler doesn't "mangle" names either if you list the name in the "exports" section of your module definition file. Chris ---------------------------------------------------------------- Chris Marriott, Microsoft Certified Solution Developer. Visit our web site at http://www.skymap.com
Thu, 13 Jul 2000 03:00:00 GMT

Ron Rubl #3 / 4	visual basic 4.0 call to borland c++ 5.0 dll -- Ron Ruble Raffles Software Development, Inc. Quote: <snip> >The Microsoft compiler doesn't "mangle" names either if you list the >name in the "exports" section of your module definition file. True; but I think Borland does that without a DEF file. This came up when VC++ 4.0 was new; a bunch of folks I worked with saw in the docs: 'use declspec(dllexport) instead of a DEF file', and went crazy trying to figure out why they kept getting 'specified DLL function not found'
Thu, 13 Jul 2000 03:00:00 GMT

Page 1 of 1

[ 4 post ]