thinBasic interface under Microsoft visual C/C++ language

**RobertoBianchi** · 18-06-2007, 08:48

Kryton,

actually I use both MS Visual C++ and GCC, and until now I didn't found problems running on different hardware platform but until now I didn't write program to use specific hardware.
In the past I used heavy the Borland Turbo C.

Never written programs for linux but only console programs on UNIX System V.

Ciao,
Roberto

**kryton9** · 18-06-2007, 23:02

I guess I am wanting that one perfect combination to do it all and it doesn't exist, except for maybe Java. But I am not ready to give up yet.
Delphi is really close to being that all perfect combo. But the challenge of c++ is there and I hate walking away from challenges, so I will struggle with it some more.

**RobertoBianchi** · 14-09-2007, 13:04

Updated today.

See http://community.thinbasic.com/index...sg8264#msg8264 for details.

Roberto.

**D.J.Peters** · 05-03-2010, 14:48

seams to be the function decoration in current MSC SDK is wrong.

the precompiled MSC example DLL export his entrys with an underscores
but thinBasic modules does not have an underscore in front of the exported names.

Joshy

**ErosOlmi** · 05-03-2010, 15:29

To keep Core engine compatible with PowerBasic/FreeBasic and C at the same time, some functions have "_" in front of the interface name.
Those with "_" in front of the name are specific for C.

**D.J.Peters** · 05-03-2010, 16:04

hello Eros
i know but will thinBasic look for both declares ?

all thinBasic lib's dosn't have an undersore but
the example shipped with the MSVC SDK have one.

Joshy

**ErosOlmi** · 05-03-2010, 16:10

Yes.

thinBasic first check if module exports "LoadLocalSymbols"
If found, it is marked an "*Basic"

If not found, thinBasic checks for "_LoadLocalSymbols"
If found, module is marked as "C"

On module unload, "UnLoadLocalSymbols" or "_UnLoadLocalSymbols" is automatically invoked depending on what was found during load.

Whenever possible I've always tried to automate interfaces in order to leave very few to the users.
To add a new module it is just needed to put into \Lib\ directory and use it in script without any worry about library and fall into the so called "dll hell"

Ciao
Eros