Re: Re: Greetings fellow programmers

Actually I am not talking about system wide DLLs. I was talking about localized software components (a.k.a. addins or plugins). They will always remain the best way to upgrade (or add functionality to) Win32 software applications without changing the main Application.

I am specifically referring to a free Image Processing Learner's Toolkit, 'Image Apprentice', that uses the DLL architecture:
www.adislindia.com/pdts.html

The Pluging Development Kit (a VC++ Project) comes for free. I was wondering how to import this in DevC++ to achieve compiler independency. That's why I asked you the question. In case you are interested in working out (or anybody else for that matter), we would be glad to acknowledge it on the Plugin Developer Network.

regards,
Divya Rathore

P.S. - Sorry about top posting. I really don't know if this is encouraged here but the new yahoo web mail with all these tables to incorporate advts doesn't make it very easy to do otherwise.


----- Original Message ----
From: Bushido Hacks <[email protected]>
To: Divya Rathore <[email protected]>; [email protected]
Sent: Monday, November 13, 2006 6:42:14 AM
Subject: [cppug] Re: Greetings fellow programmers

I'm not a fan of Dynamic-link libraries (a.k.a. DLL files). In fact,
the reason why I wrote the tutorial the way I did was so that DLL
files were NOT used.

Currently, the instructor for my OpenGL class, of which the programs
are written in C++, uses an old version of Borland which is compatible
with an old version of GLUT that requires a DLL file be placed in the
system folder. Something I wasn't very comforable with. Aside from
completing the weekly assignments he gives us, my own personal
assignment is to create better version of his programs that do not
require the foreign DLL file to run them.

The DLL file that he uses makes in COMPLETELY impossible for me to run
my programs remotely from a removable media.

Another important reason why DLL files construction is not used is
because of the redundancy which leads to greater problems including
security holes and stability. (See
http://en.wikipedia .org/wiki/ DLL_hell ).

DLL files are not worth the trouble. While shared objects are a good
idea, saving them as DLL files is irksome.

On 11/12/06, Divya Rathore <divyarathore@ yahoo.com> wrote:
>
>
>
> I would definitely be interested if you could detail more about writing dlls.
>
> regards,
> D. Rathore
>
>
> ----- Original Message ----
> From: Bushido Hacks <bushidohacks@ gmail.com>
> To: cppug@yahoogroups. com
> Sent: Friday, November 10, 2006 10:46:32 AM
> Subject: [cppug] Greetings fellow programmers
>
>
>
>
>
>
> My online handle is Bushido Hacks. I've been transitioning away from
> my former online moniker of EyesOnlyUS.
>
> I am a computer science major from St. Louis. I intend to graduate
> from college in the spring.
>
> Recently, I wrote instructions for obtaining and using GCC and the
> GLUT graphics library. While this software tutorial does not go in to
> telling people how to program in C, C++, or OpenGL using C or C++, it
> does provide step by step instructions for people intereste in
> programming especially Windows users.
>
> I've recieved over 250 hits since it was upload on Monday and couple
> of positive responses.
>
> My instructions are available at
> http://www.bushidoh acks.com/ tutorials/ gcc.php
>
> I would like to improve these instructions such that I can use MinGW
> and a Windows port of GLUT. Any suggestions as to how I can improve
> my tutorial?
>
> 
>
>
>

-- 
BushidoHacks. com





[Non-text portions of this message have been removed]