|
-
May 11th, 2010, 07:43 AM
#1
Rules for DLL Function Signatures
Hi,
Are there any specific rules as regards parameters that make up a DLL function signature which is exposed to the outside world ?
In addition, Is it an accepted practice to have DLL function signatures which
1.Take class objects as parameters (object parameters, pointer to object or reference to object)
2. Return class objects as parameters (object parameter, pointer to object parameter, or reference object)
I suppose it is acceptable to return an object pointer from a DLL, because that is one of the ways in which plug-ins are implemented (where the return type is an Interface pointer)
Please do let me know.
The DLL is expected to be consumed by C or C++ clients.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|