🚀 go-pugleaf

In article <kylep.724046411@teal> kylep@teal.csn.org (Douglas Kyle Pierce) writes:
>philco@microsoft.com (Phillip Cooper) writes:
>
>>In article <kylep.723342558@teal> kylep@teal.csn.org (Douglas Kyle Pierce) writes:
>>>I am trying to link existing QuickBasic code with C++ code. Unfortunately,
>>>it seems that only Microsoft C/C++ can be linked with any of QuickBasic
>>>or Visual Basic versions (I have access to several versions). This is
>>>according to the documentation, and my limited experiments.
>>>
>>>Has anyone succeeded in linking any Basic code with Borland or Turbo C++?
>>>I would greatly appreciate hearing from you. Thanks.
>>>
>>>Kyle Pierce
>
>>Assuming that Borland C++ produces standard Windows DLL's, you should
>>certainly be able to to call routines in the DLL from Visual Basic.
>>Of course, why you would want to use Borland C++ escapes me :)
>
>>Phil
>
>Well, from Windows of course I can do that! And I pretty much agree, in
>that case VB is the best tool for front end work. But my main problem is
>in making DOS programs, not Windows. Another story entirely, when it comes
>to linking stuff together. 
>

I've spoken to people who say it works (with Borland C++), and I've also
spoken to people who say it doesn't work.  I do know that we have not
done any comprehensive testing on this and certainly do not guarantee
compatability with any other language vendor's products.

>Also, let us not forget that we need C/C++ to make DLL's and custom
>controls, and enhance VB's performance in many ways. Tell me it doesn't
>need it?!

Actually, you can create DLL's with a number of languages, including
FORTRAN, Pascal, Assembly, etc.  You certainly do NOT need C/C++ to 
create DLL's (Although it is required for custom controls).