OOP lib

SofT MANiAC · Post by **SofT MANiAC** » Mon Feb 25, 2008 9:18 pm

How can I use classes from OOP libs in PB?

Trond · Post by **Trond** » Mon Feb 25, 2008 10:34 pm

It depends on what language they are written in. But the interface keyword can be used.

SofT MANiAC · Post by **SofT MANiAC** » Tue Feb 26, 2008 6:48 am

Trond wrote:But the interface keyword can be used.

How can I apply this? small example would be cool

any idea?

Rook Zimbabwe · Post by **Rook Zimbabwe** » Tue Feb 26, 2008 7:05 am

OOP has the advantage of being able to make tiny little problems into complex and frustrating HUGE problems...

That said... the OOPfiles speak here:

http://www.purebasic.fr/english/viewtop ... t=oop+pure

here:

http://www.purebasic.fr/english/viewtop ... t=oop+pure

and here:

http://www.purebasic.fr/english/viewtop ... t=oop+pure

I frankly cannot see why you would wish to torture yourself that way. My framework is slightly OOP like, but instead modified for inline ASM stack. Well, I think it is!

SofT MANiAC · Post by **SofT MANiAC** » Tue Feb 26, 2008 9:01 am

@Rook Zimbabwe
10x man, but I know what is OOP (I'm using PureObject by inc).

But I can't understand how to wrap classes from lib

srod · Post by **srod** » Tue Feb 26, 2008 11:07 am

It depends how the methods are wrapped up inside the lib. If it is a COM dll, well that requires use of interfaces and GUID's etc. There's enough examples in these forums of doing that kind of thing.

If you're talking about a static library built from an oop language (like Emergence Basic for example) then you may be able to get away with importing the functions by hand and building an interface yourself - it depends how the methods are built to accept parameters and whether they are to accept a *this type parameter etc. If this is not the case then you may just be able to import the functions for a c-style wrapper etc.

You will need a good definition of the underlying class; it's methods and private data etc. and you will need to know how the method names are mangled when placed into the static lib. oop languages often mangle the names by combining the class and method names etc.

So, there are a lot of 'ifs' and buts' with this I'm afraid.

SofT MANiAC · Post by **SofT MANiAC** » Tue Feb 26, 2008 11:13 am

@srod
thanks for info!
ok, i wanna make a wrapper for PopCapFramework (SexyApp) (VC++)

srod · Post by **srod** » Tue Feb 26, 2008 11:23 am

Bloody hell; good luck with that!

SofT MANiAC · Post by **SofT MANiAC** » Tue Feb 26, 2008 11:58 am

srod wrote:Bloody hell

Yep

Rook Zimbabwe · Post by **Rook Zimbabwe** » Tue Feb 26, 2008 4:22 pm

I knew it!

I still reccomend HGE

SofT MANiAC · Post by **SofT MANiAC** » Tue Feb 26, 2008 4:29 pm

Rook Zimbabwe wrote:I knew it!
I still reccomend HGE

ok

I'll try it

Kale · Post by **Kale** » Tue Feb 26, 2008 7:34 pm

Rook Zimbabwe wrote:OOP has the advantage of being able to make tiny little problems into complex and frustrating HUGE problems...

I was once under that impression until i fully understood OOP.

srod · Post by **srod** » Tue Feb 26, 2008 8:06 pm

Well, let's not go there again.....

but I'm with Kale!

OOP is very very very very nice!

byo · Post by **byo** » Sun Aug 31, 2008 7:05 pm

Is there a simple example on how to wrap classes from a DLL in Purebasic?

Not because I like OOP, but because I know there are a lot of great engines/DLL that uses OOP and I'd like to have the functionality/commandset in PB.

srod · Post by **srod** » Sun Aug 31, 2008 9:04 pm

Well, difficult to comment without knowing more. If you are asking if you can create a dll in PB which contains OOP classes which you can access from a client program - then yes; no problam at all. I am currently working on such a project in which a dll exposes 4 classes and over 120 methods between them.

The dll exports a function which simply initialises a new instance of the class and returns a pointer to the newly created object etc. Very simple, very effective.

All the client program needs in order to make use of the object returned from the dll is a list of all the interfaces exposed by the dll and the methods therein etc. and that's it.

If this is the kind of thing you are asking about then I should be able to knock up a simple example for you. It would have to wait until tomorrow though.