Below are some series of lesson which will give the basic (definition) level of insight to data structures.
Printable View
Below are some series of lesson which will give the basic (definition) level of insight to data structures.
Here is a very simple and a conceptual view of the data structures. This article doesn’t describe the concept in detail but just shows the overview. Most of the definitions can easily be found over Wikipedia. After the conceptual lessons more detailed lessons will be presented that will have more concrete examples.
Click here for full article
http://bytebeats.com/2011/07/27/conc...ucture-part-1/
The lesson continues on Data structure for Primitive Type but before learning this lesson you should read this.
http://bytebeats.com/2011/07/27/conc...ucture-part-1/
Primitive Type: The following primitive types are used in data structures.
Click here for full article
http://bytebeats.com/2011/08/08/conc...ucture-part-2/
The lesson continues on Data structure for Composite Types but before learning this lesson you should read this.
http://bytebeats.com/2011/08/08/conc...ucture-part-2/
The following types are the composite types
Click here for complete article
http://bytebeats.com/2011/08/10/conc...omposite-type/
I think you need to define your target audience. If this is going to be a basic introduction you must use a basic terminology. For example someone who doesn't know the meaning of a float most likely won't get any wiser by having it explained in terms of precision. And someone who knows what precision means won't need your explanation of a float.Quote:
Originally Posted by bytebeats
I think you should spend more time elaborating on the classification into primitive, composite and abstract types. What exactly is the basis for this classification? If any, what's the difference between a data structure and a data type?
Also the information you provide is full of strange claims and inconsistensies. For example you say that a Boolean is "mostly used for comparisions". Aren't you confusing Boolean as a data structure with boolean as the result of a logical evaluation? You say that a String is "a representation to a set of characters". Is a String really a set, isn't it a sequence? Why do you list Float and Double as separate types but not even mention the variations of Integer? This is a confusing mix of level of detail. Furthermore, must a Double really have 64 bits as you state? And what does "used for more complex arithmetic operation" mean? Is Double supporting operations Float doesn't support?
I could go on and on but I think you get my point. It's a good start but it needs improvement.
Good luck.
hey nuzzle
You are right you pointed out some really good areas thanks for that. I agree with most of them i will fix them ASAP.
/A
Here's something similar to your project. Maybe you can get some ideas,
http://en.wikibooks.org/wiki/Data_Structures
Hey, great link, nuzzle! People seem to keep asking about good sources to learn about data structures and I never have a good link to give them. Now I do!Quote:
Originally Posted by nuzzle
Edit: In my haste, maybe I wasn't as diplomatic as I should have been: bytebeats, your stuff looks pretty good too (subject to nuzzle's comments). I was simply reacting to the fairly comprehensiveness of the wikibooks.