dev-cpp-users Mailing List for Dev-C++

<html><div style='background-color:'><DIV>i've found a page on DLL's.</DIV>
<DIV>Here's the url</DIV>
<DIV><A href="http://www.iseran.com/Win32/FAQ/section7.html#113">http://www.iseran.com/Win32/FAQ/section7.html#113</A></DIV></div><br clear=all><hr>MSN Photos is the easiest way to share and print your photos: <a href='http://go.msn.com/bql/hmtag3_etl_EN.asp'>Click Here</a><br></html>

<html><div style='background-color:'><DIV>
<P>Hey Jason,</P>
<P>Nice description, very informative. Thanks from me!</P>
<P>Daniel</P>
<P><BR><BR>&nbsp;</P></DIV>
<DIV></DIV>
<DIV></DIV>&gt;From: "Jason Hardman" <JAS...@BT...>
<DIV></DIV>&gt;To: "Dev-C++" <DEV...@LI...>
<DIV></DIV>&gt;Subject: Re: [Dev-C++] DLL's? 
<DIV></DIV>&gt;Date: Mon, 17 Dec 2001 02:15:58 -0000 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Seeing no other answers yet so I'll say what I know. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;A DLL or Dynamic Link Library is a way of way of distributing code that 
<DIV></DIV>&gt;performs a task and is reusable. An ordinary library contains code for 
<DIV></DIV>&gt;various functions, like the standard C and C++ libraries, and when used the 
<DIV></DIV>&gt;library itself is added to the executable file and the only thing the 
<DIV></DIV>&gt;compiler needs to know is the function prototypes. The code is connected to 
<DIV></DIV>&gt;yours by the linker, which can sort out things like function call 
<DIV></DIV>&gt;addresses/offsets. While this is fine for small and simple programs it 
<DIV></DIV>&gt;becomes a problem for if you use many libraries because each adds to the 
<DIV></DIV>&gt;size of your executable, and having several programs that use the same 
<DIV></DIV>&gt;libraries will mean that there will be a copy of the same functions within 
<DIV></DIV>&gt;several different executables. If a library changes, to fix a bug for 
<DIV></DIV>&gt;example, then your code would need to be recompiled and the entire thing, 
<DIV></DIV>&gt;which may be several megs, will need to be redistributed, or you would at 
<DIV></DIV>&gt;least need to generate a patch. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;With a DLL the code is put into a seperate file and the system can be 
<DIV></DIV>&gt;instructed to load in a particular DLL when needed, so your program can take 
<DIV></DIV>&gt;advantage of the functionality the DLL provides. So the main executable is 
<DIV></DIV>&gt;smaller for not having the extra code, you only need one copy of a DLL, 
<DIV></DIV>&gt;saving disk space, and if several programs all need the same DLL at the same 
<DIV></DIV>&gt;time then only one copy needs to be loaded into memory. An added benefit is 
<DIV></DIV>&gt;that if you need to update the DLL, fixing bugs or adding new functionality, 
<DIV></DIV>&gt;then all you need to replace is the DLL and you don't have to update all 
<DIV></DIV>&gt;your executable that use it. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;That's the basic idea of a DLL, unfortunately I don't know much about 
<DIV></DIV>&gt;creating and using them. I do know to use them then you have to instruct the 
<DIV></DIV>&gt;system (Windows) to load in the DLL and you need to aquire information from 
<DIV></DIV>&gt;the DLL to be able to call a specific function within it. Sometimes when 
<DIV></DIV>&gt;using a particular library (such as DirectX) this part is done for you. 
<DIV></DIV>&gt;Maybe there is a guide on the web somewhere that tells you the details of 
<DIV></DIV>&gt;creation and use of DLL's. I think that different programming languages 
<DIV></DIV>&gt;would have different mechanisms for making use of DLL's that fit with the 
<DIV></DIV>&gt;complexity of the language. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;I hope this is of help, Jason. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;----- Original Message ----- 
<DIV></DIV>&gt;From: "Johnny Dessì" <JD...@DA...>
<DIV></DIV>&gt;To: "Dev-Cpp" <DEV...@LI...>
<DIV></DIV>&gt;Sent: Sunday, December 16, 2001 5:38 PM 
<DIV></DIV>&gt;Subject: Re: [Dev-C++] DLL's? 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; &gt; Nice Question! 
<DIV></DIV>&gt; &gt; I'd like to read some answer! 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; _______________________________________________ 
<DIV></DIV>&gt; &gt; Dev-cpp-users mailing list 
<DIV></DIV>&gt; &gt; Dev...@li... 
<DIV></DIV>&gt; &gt; https://lists.sourceforge.net/lists/listinfo/dev-cpp-users 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;_______________________________________________ 
<DIV></DIV>&gt;Dev-cpp-users mailing list 
<DIV></DIV>&gt;Dev...@li... 
<DIV></DIV>&gt;https://lists.sourceforge.net/lists/listinfo/dev-cpp-users 
<DIV></DIV></div><br clear=all><hr>MSN Photos is the easiest way to share and print your photos: <a href='http://go.msn.com/bql/hmtag3_etl_EN.asp'>Click Here</a><br></html>

Seeing no other answers yet so I'll say what I know.

A DLL or Dynamic Link Library is a way of way of distributing code that
performs a task and is reusable. An ordinary library contains code for
various functions, like the standard C and C++ libraries, and when used the
library itself is added to the executable file and the only thing the
compiler needs to know is the function prototypes. The code is connected to
yours by the linker, which can sort out things like function call
addresses/offsets. While this is fine for small and simple programs it
becomes a problem for if you use many libraries because each adds to the
size of your executable, and having several programs that use the same
libraries will mean that there will be a copy of the same functions within
several different executables. If a library changes, to fix a bug for
example, then your code would need to be recompiled and the entire thing,
which may be several megs, will need to be redistributed, or you would at
least need to generate a patch.

With a DLL the code is put into a seperate file and the system can be
instructed to load in a particular DLL when needed, so your program can take
advantage of the functionality the DLL provides. So the main executable is
smaller for not having the extra code, you only need one copy of a DLL,
saving disk space, and if several programs all need the same DLL at the same
time then only one copy needs to be loaded into memory. An added benefit is
that if you need to update the DLL, fixing bugs or adding new functionality,
then all you need to replace is the DLL and you don't have to update all
your executable that use it.

That's the basic idea of a DLL, unfortunately I don't know much about
creating and using them. I do know to use them then you have to instruct the
system (Windows) to load in the DLL and you need to aquire information from
the DLL to be able to call a specific function within it. Sometimes when
using a particular library (such as DirectX) this part is done for you.
Maybe there is a guide on the web somewhere that tells you the details of
creation and use of DLL's. I think that different programming languages
would have different mechanisms for making use of DLL's that fit with the
complexity of the language.

I hope this is of help, Jason.

----- Original Message -----
From: "Johnny Dessì" <jd...@da...>
To: "Dev-Cpp" <dev...@li...>
Sent: Sunday, December 16, 2001 5:38 PM
Subject: Re: [Dev-C++] DLL's?


> Nice Question!
> I'd like to read some answer!
>
>
>
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

Hi again!

I like answering your questions sometimes. It's good practice for the skills
I have managed to develop so far. I assume it's for a lesson or such?

If you are generating an output string then using a string to store it isn't
hard, all you need to do is append each letter as it is generated onto the
output string, when you output it all you do is just reinitialise it to an
empty string to start again. The C++ std::string would be best (use += to
append), but it could be done with a C null terminated string, with a little
more work, just keep track of the index (or pointer) into an array, move it
on as you add each letter, and null terminate it before displaying. Just
makesure that you don't overrun the arrays bounds.

If you are looking to use a container type then a queue would be suited,
push your letters into the queue and then, to display them, just pop them
off one at a time until the queue is empty.

As I like to I have made a small program that follows what you have said
(AFAICT), but I don't know all the rules so you can implement the rest
yourself.

Jason.

----- Original Message -----
From: "chromatonus 712" <chr...@ho...>
To: <dev...@li...>
Sent: Sunday, December 16, 2001 8:23 PM
Subject: [Dev-C++] encoding


> using the numerical val of each letter a=1, b=2... z=26, and rules as
> follows:
> rule 1... multiply its numberical val by 2
> rule 2... divide its val by 3...
> rule 3
> rule 4    (irrelevant, i can take care of them)
> rule 5
>
> so an input of C1B2F3$ would provide an output of GQI:
>
> C is 3, which becomes a 6 by rule 1 (the number right after) so counting 6
> letters from A, the result is G. B is 2, using rule 2 eval to 10 (ommitted
> here) so counting 10 letters from G is Q. the $ prompts the output.
>
> When entering a new set like k2j3h2k1$  or b3n2j5$ or more, always start
> counting with A.
>
> i tried to store the output letters in link-ed list but don't work. can
you
> please help asap? thank you!
>
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>
>
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users