DLL coding dilemma...

Shy Agam

Hey all, I'm facing a small dilemma... I'm currently coding a dll which will be used in one of my projects. As I go further and further with the development of my dll, it becomes clearer that a specific coded dll would serve me better as opposed to a general coded dll, when it comes to both performence and coding issues. By specific coded dll I mean that I write my dll to be used only with my current project. If I'll ever want to use it in another project, I'll have to make changes. What should I do? Which is a better programming practice? Not really sure where to post this question... Maybe I'll post it in another forum as well. Thanks in advance, Shy.

realJSOP

If you're going to make it specific to one program, what's the point in making it into a DLL. You way want to look into putting any of the truly common functions into a .LIB, and then linking the .LIB to your apps while putting the app-specific stuff into the app itself. Of course, I'm assuming that you're using C++ and not some abomination, like VB. I don't know if VB lets you create LIB files.

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

Shy Agam

I need to inject my dll into every running process... :)

realJSOP

Where, in your previous description, did you mention that. It annoys me to waste my time answering a question only to find out that the entire list of requirements hasn't been specified. Further, why would you need to inject your DLL into every running process? I hope you're not doing this for distribution in something like a spyware app.

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

Dai Hui

Maybe you can split it into two dlls?

Dai Hui LW-WORKS Software - Creator of Clipboard Recorder Windows Clipboard utility