Re: keep interface private to dll?
- From: "mayayana" <mayayanaXX1a@xxxxxxxxxxxxxxxx>
- Date: Mon, 09 Jan 2006 06:04:24 GMT
If by interface you mean that you want to
have an internal class object, just set its
instancing to Private (1). That will make
it like a class in an EXE - internal to the
DLL. Multiuse (5) makes it a class that's
visible and creatable from outside. And
PublicNotCreatable (2) makes it a class
that's visible from outside but cannot be
directly created. That's usually used for
a custom object that you provide as a
function return. As in:
Set obj = DLLClass.GetSomething
DLLClass would be a public class with
instancing of 5. obj would represent a class
instanced as 2.
--
mayayanaXX1a@xxxxxxxxxxxxxxxx
(Remove Xs for return email.)
Dushan Bilbija <dbilbija@xxxxxxx> wrote in message
news:#wZE57MFGHA.216@xxxxxxxxxxxxxxxxxxxxxxx
> hello,
>
> rackin by brain, but can't find a way to do this. i'd like to implement an
> interface, which i can use to perform a handful of common functions across
> related objects.... BUT.... i want this interface to be private to the
dll.
>
> any way to do this? tried, friend functions, underscores, private
> instancing.... nothing
>
> any help would be greatly appreciated.
>
> dushan bilbija
>
>
.
- References:
- keep interface private to dll?
- From: Dushan Bilbija
- keep interface private to dll?
- Prev by Date: Re: How to declare 2-dimensional dynamic array?
- Next by Date: How to combine 2 parameters into one and later extract each of them?
- Previous by thread: Re: keep interface private to dll?
- Next by thread: Re: keep interface private to dll?
- Index(es):
Relevant Pages
|
