1. .dll files -- possibly [OT]

Hello,

Could someone explain to me the use and more
importantly the benefits of .dll files?  They seem to
me to be basically include files (I'm most likely
mistaken), and I'm wondering why use a .dll file vs a
standard include file?  What can be done using a .dll
file that cannot be done with includes?

(Excuse my ignorance -- there is a wealth of knowledge
being passed around this board, and I thought I'd ask
the experts... :)

Thanks,

Chris

new topic     » topic index » view message » categorize

2. Re: .dll files -- possibly [OT]

----- Original Message ----- 
From: "Chris Saik" <csaik2002 at yahoo.com>
To: "EUforum" <EUforum at topica.com>
Subject: .dll files -- possibly [OT]


> 
> 
> Hello,
> 
> Could someone explain to me the use and more
> importantly the benefits of .dll files?  They seem to
> me to be basically include files (I'm most likely
> mistaken), and I'm wondering why use a .dll file vs a
> standard include file?  What can be done using a .dll
> file that cannot be done with includes?
> 

DLL stands for Dynamical Linked Library. The file is only loaded into memory if
its needed, and automatically removed from memory when no other program is using
it. A single DLL is loaded into RAM no matter how many different programs are
using it.

The 'include' idea is a Statically loaded library. Each program that uses the
same include file, loads their own copy of the file into RAM.

So to put is simply, a DLL is a library that is sharded in RAM and is
independant of the application program.

-- 
Derek

new topic     » goto parent     » topic index » view message » categorize

3. Re: .dll files -- possibly [OT]

Ahhh.  That clears it up.  Thanks Derek.


--- Derek Parnell <ddparnell at bigpond.com> wrote:
> 
> 
> ----- Original Message ----- 
> From: "Chris Saik" <csaik2002 at yahoo.com>
> To: "EUforum" <EUforum at topica.com>
> Subject: .dll files -- possibly [OT]
> 
> 
> > Hello,
> > 
> > Could someone explain to me the use and more
> > importantly the benefits of .dll files?  They seem
> to
> > me to be basically include files (I'm most likely
> > mistaken), and I'm wondering why use a .dll file
> vs a
> > standard include file?  What can be done using a
> .dll
> > file that cannot be done with includes?
> > 
> 
> DLL stands for Dynamical Linked Library. The file is
> only loaded into memory if its needed, and
> automatically removed from memory when no other
> program is using it. A single DLL is loaded into RAM
> no matter how many different programs are using it. 
> 
> The 'include' idea is a Statically loaded library.
> Each program that uses the same include file, loads
> their own copy of the file into RAM.
> 
> So to put is simply, a DLL is a library that is
> sharded in RAM and is independant of the application
> program.
> 
> -- 
> Derek
> 
>
> 
> 
> TOPICA - Start your own email discussion group.
> FREE!
>
>
>

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu