A simple sort program...

hello all,there are many alogrithms for sorting data..M here providing just another algorithm for sorting integers ..i said just another , coz it follows a diffrent algorithms from qucik sort,heap,sort etc..i think its a quick one and efficient too...

here is the source code
http://www.esnips.com/doc/9b765853-d060-40e2-9758-5de0e5b60db9/sort2


ask at abhi1iips@gmail.com for any queries

Reading bit pattern of a datatype

here nothing to discuss much for the introduction....i will give the c++ code for reading the bit string of an integer..the program is in a very straight forward manner.....

#include iostream
#include conio.h
#include stdio.h
#include vector
//as this blogger tool doesnt allow some syntices ,so i consider here you will be doing it urself,we have to include vector header file besides some general i/o libraries...

using namespace std;int main()
{vector v;
int x =2000;
int collect;

int counter = 8*(sizeof(int));
for( int j=0;j{collect = x&1;
v.push_back(collect);
x >>= 1;
} for(int i=counter-1;i>=0;i--)
{ cout v[i];//i am not using the complete syntx due to restriction made

//by the blog editor
}
getch();
return 1; }


here i am reading the bit pattern of an int,,,applying little modifications..we can read for other data types too....hope this helped....

Why we need headers in c too ??

The title "Why headers are necessary in c?", by this title its not meant at all that they are not necessary in c++. this sentence becomes specific in case of c just because of the loose control of c standard over this crucial issue,which makes c a little bit non-resistant to complilation errors.As we all know that C is not much concerned about function declarations.If you call a function without declaring it anywhere(of course it should have a defined block of code) then c wont have any problem with it, it will compile it correctly and you may get the correct results till you call the function with proper arguments. the last clause that "till you call the function with proper arguments " makes a point of interst, what happens if someone calls a function with bad arguments (different no of arguments and type mismatch), nothing!!! here our compiler acts like a dumb one...it just assumes that the argument's list it has been provided is correct and pass it to the function's actual implementation(definition) and at that place errors may occur and it will be very hard to detect.As compiler wasnt even having some other source to match the correctness of the arguments, so wat it does in the case explained earlier was completly justified.
take for an example
a function whose body is like this....
void myfunc(int a , float b){
/*some code*/
}
now suppose there is no declaration anywhere
and we call the function
myfunc(23,54);//compiler will claim no error ,considering there is a function which takes two integer arguments
so here we are passing both integer arguments,which may cause a subtle problem because float was expected as second argument.
here we come up with the 1st and very basic requirement of function declarations (As declarations are generally meant to be done in header files ,so talking about all this is relevant)
1.so to detect these type of errors and allow comipiler to do some type promotion if necessary right at the compile time
2.And the second and very known to all requirements is to save the typing time in making declarations and hence ensuring no typing errors too....
Now in case we are using libraries or simply says we are to call some external functions.
suppose there are two function with the same signatures.
lets suppose the function name is func1(int ,float), and there are two bodies of this function (i mean two differennt versions with same signature, means they are made by two different person or say same also and the name of the two functions was kept same either accidently or intentinally for the purpose of relevant name.) As here we are trying to illustrate the importance of the header files in this scenario so we will first consider the case of absense of any header file (obviosly those one which contain the declrartions for the two functions). So as the tendency of c compiler is if it dont find any declarations then in that case it doesnt have any problem with that it simply guesses the structure of the function's prototype by the calling place. so it wont have any problem , the source file be compiled successfully..no problem till this point..now when it comes the chance for linker to do its job, then what linker will do is just link the function whichever will be found at first (As stated earlier there are two functions of the same prototype) .Even up to this point problem doesnt get clear about which i am trying to pull the attention ,as we don't see any error (neither compilation error nor linker error) thats y.
Now answer the following questions....
1. which version did u intend to call (here we already know that we have two functions of the same name placed in different obj files and libraries).
2. Is it gauranteed that the version you called has been linked ,isnt there any possibility that the other version got linked instead of the desired one.

And if this type of problem occured then it will be very difficult to trace out.
NOW HOW THE INCLUSION OF HEADER FILES SOLVES THIS TYPE OF RARE BUT VERY DIFFICULT TO TRACE ERRORS.
very simple, if u include the header files for both of the functions then compiler will find a multi decalaration problem in the source code and will notify about it ...souce code will not be complied and hence in this way we will get notified very earlier about a big and diffiult to find problem.
Now we will see the essence of header files from the library's vendors point of view. will be continued....
Now we will understand from library's vendor's point of view..
If you are providing some library then (in case if you want to sustain the proprietary rights then you will never like to give the complete source code .) you will obviously provide that in the form of object files or compiled libraries.
Now 1. how your user will know that wats there in the library??
2. And you will very probably need some declarations for your functions to be called with proper arguments and allowing the compliler to do some necesaary optimizations in terms of casting etc..
so these two things can be fulfilled in a very convinient way by providing header files...in which user can see wat functions are there in the library he is using and how to call them....

declaration vs definition

These terms have been oftenly confused with each other.Reason behind this is we cant observe it (in case of variables) when we are working in a single file.Lets see why i say like that..let me first briefly explain these two terms...

1. declaration.... its just an acknowledgement to the compliler about the blueprint of some entity. Be it a varaible or a funtion.By putting blue print i just mean that..the necessary information(characteristics) about the entity. so here complier doesnt allocate any memory to the entity(Remember functions also need memory not only variables). It just takes the information and ok..nothing is done from compiler side as far as allocation issues are concerned!!.So the entity declared doesnt exits in memory till now. so what to do , our target is to use those variables and functions...so here we come up with definitions.

2.Definition...

This is the thing which brings some enitity into its real existance.

The value is given to the variable(if u do it explicitly then its ok , your value will be assigned to the variable otherwise you will get the garbage value). So here the memory is allocated for the entity and from hereafter it is present in the memory.

lets observe it in a program.

twoterms.c

#include...........
/*include the things you need
,i am not writting them here*/
extern int globalvalue;//this the case of pure variable declaration
void myfunction1(int,float);

/*A function declaration...as there isnt any body for the function ,so no need of memory, obviosuly compiler doesnt need to allocate any memory for this one, very clever!!!*/

void main()

{

int i;//remember its a declration as well as definition
printf("the value of i is %d",i)//garbage value will be dsiplayed

int i2=0;//declaraions as well as initialization
}

Easter eggs in a software

An Easter egg is a hidden functionality(set of tasks which however may or may not be part of the main system,it totally depends on the programmer's wish..whatever he likes to do he will do,it means there is not any preset standard to enforce the programmer to provide some specific functionality.) in a software, Which is not directly visible to the users however depending on some specific events they come into action....Now we will illustrate it in a very simple way by taking an example of a html page. In this page, suppose i want to show a help section which needs to be some event specific..i mean some particular event will trigger it.
So i say if u type help anywhere in the page , You will be taken to the help section....so this is known to me only ...however when users will go through it they will be knowing it afterwards. so obviously this is something hidden and about which there is not any message or say informatiion.

Now use this code (You are taken to google help section after typing the word "help", so this is an easter egg of this webpage.) in understanding this term......here goes the code!


http://www.w3.org/TR/html4/loose.dtd">
var accumulator = new Array();
var match_it = new Array();match_it[0]= 72;
match_it[1] = 69;
match_it[2] = 76;
match_it[3]= 80;
var index = 0;
var started = 0;
window.onkeyup = keyup;
function clearString()
{index = 0;}
function keyUp(e)
{var mykeycode = e.keyCode;
var temp = parseInt(mykeycode);
accumulator[index] = temp;

index++;
if(index==4)
{
var matched = 0;
for(i=0;i<=3;i++)
{ if(accumulator[i]==match_it[i])
{
matched++; } } }
if(matched==4)
{ alert("you typed help");
window.location = "http://www.google.co.in/help" }
if(started==0)
{ var t = setInterval("clearString()",2500); started = 1; }
}
body onkeyup="javascript:keyUp(event);">

press and hold any key, then release it to fire the keyup event

Making an innovation help+

Livingness vs non-livingness

this article is motivated from my belief that the beauty of the livingness is not the fruit of only it's capability but also we have non-livingness which shares a great proportion in the credit for the evolution of livinenss. for this dicussion to be taken forward i just need to share what i think about these two independent terms. so what livingness is just a perpatual fight for one's existance ,it just continues to strive for being in the state in which its comfortable and enjoys its existance, however feelings,sentiments,individuality all are derived parameters which alltogether keep livingness in action and focussed to its motive. And what the non-livingness is just absence of all the parameters mentioned above. However being ignorant to the fact of its physical existance Non-livingness has always supported livingness for the actions of livingness to be exceuted and achieving the goals. If the whole planet were alive(i mean each and every entity, constituent of the system) then the livingness wudnt have been that beautiful as it is and as it feels to livingness at least.Reason behind this is so simple to understand that if all were alive they all have had some motives and obviosuly they would suffer from ill feelings i mentioned above and conflict of motives,methods of workings wud stand against the rise of its own.so it wont be an exaggeration to say that livingness depended much on non-livingness. and this dependency is proliferating day by day, one day surely gonna come when majorities of human(the main living entity responsible for structuring and hence assigning non livinness its work) actions will be executed by non-livingness while livingness will have to witness the power,the efficiency,the altrusim it possesses. this all should be very much apparent if you just observe your daily shedule and involvement of machines in that. but wait m not critisizing livingness, this was just to realize the power of non-livingness. by the facts(my observations very common in fact) drawn above i may be appearing to say that "by getting assisted by non-livingness livingness has lost its capability", but its not that.in fact it has enhanced it's capability with the help of blend of power of both.this is how i agree with the proposition (which i make here in this article) that non-livingness has the power, the power of efficiency,correctness,unbiasedness and immunity to pain and tiredness. someone may disagree and award the whole credit to only livingness by arguing that non-livingness was nothing without livingness's support who could assemble non living things to behave as a working unit otherwise it was an useless piece of physical structure. But this argument can be strongly opposed by the fact that livingness sees the usability in terms of its needs, so there is not any global reference to measure the usability. If livingness has given a shape, a structure to non-livingness then this is for it's own needs only.So its not only the liningness which should be given the whole credit but also non-livngess without which things were not be as beautiful as today.SO LIVINGNESS OWES MUCH TOO non-livingness.

What humanity means to me

humanity means....to first realise da fact that we are human beings (the only blessed living animal with consciousness and logical thinking )...humanity refres to the maximum use of these abilities in order to achive the ultimate goal(however goals are matter of individual interests and understandings of life) while hurting nobody and helping others as if we were doing it for ourself only.....

The truth of information hiding and encapsulation

As many people oftenly get confused in the jargon of these two closley interrelated terms(even me too ). Here i am jotting down what i could percieve about thses two gaints (ya they are!).
so at the very beginning i would like to tell you that there is not any ultimate defination (global agreement) of these terms. they have different meanings in different context. however i could clasify (in fact many experts also suggest the same thing) the two meanings in 1. Design perspective 2. Programming perspective


Design perspective:
lets first talk about the design principle.....feeling comfortable tll this point?!!
allright , one of the main motives of the design is to understand and control the complexity of the system (the problem). so we tend to redue the complexity by means of bunddling related things together.These bundles represnts a working unit(as elementry as possible) of the system. Now as these bundles are the actual c0nstructs of the system , so obviosuly they need to interact with each other(if they get enforced in a complete isolation then the system would become a simple wizzard in which there are discrete components , and no component knows about any other, each may perform its own job but it will be very difficult for others to take benifit of the job done, so not forming the system.). Now here we need to provide some mechanism by means of which one component may inetract with others so as to take benefits of the functioanlities in getting its own working done. Now this mechanism is called interafce. This interface will be the communication point of one bundle to another. so obviosly however a good design considers and tends to minimize these connections for achieving modularization. so this is all about encapsulation at design level. at this stage of design one can see the effect of change of one bundle on others, so one has to think in terms of protecting one part from the change (intented or accidental at the run time) of the other part..this introduces the great concept of information hiding. lets also have a glimpse of the dependency or interrelation of one to the other. Encapsulation itself is not an isolated concept , for example ..how to decide that which things are related and hence should be kept together in a spearate bundle (the encapsulated entity) , this problem gets solved by the concept of information hiding....it tells that, group only those elements together which correspond to a design decision to be hidden and prevent others by decreasing the connections to this group . so this shows the dependency of encapsulation on information hiding. information hiding also incorporates encapsulation , because by encapsulating we are hiding information from each other.


Programming perspective:
the fact that data and the methods to operate this data are shielded in a physical boundry(say a capsule and in object oriented programming language we call it an object) is called encapsulation.
however the concept of encapsulation at this level is to bring out the compartmentalization of the related things. this does not consider hiding something . at this point (As we havent introduced information hiding till now, by saying so i dont mean at all that these two things exist totally in isolation and dont even reject their concurrent existance, in fact they are oftenly concurrent as i discussed in the design perspective. so saying "at this point" i simply intend to comfortably illustrate the difference bw the two terms) there is not any comcern of hiding information objects (the capsule in the encapsulation analogy) from each other. Now programmer checks if there is some vital data(information) mishandling of which may cause dire(or even a little undesired too) consequences. so now he/she will tend to protect (by hiding from other part) that data by some mechanism (here comes access modifoers). And hence he by doing so successfully hidden the data from the outside world.
From the above discussion it would be clear that encapsulation doesnt guarantee information hiding (protection of data form accidental manipulation). A good object oriented programming incorporates both concepts in concurrent manner.

hope this was helpful to you...the article presented here is motivated by the perception made by the study of different articles found on the internet. this is an abstract of all thesis and lectures made by different experts..this doesnt reflect thinking of a single mind (just because thes two terms are too controversial...people still have much different opinions as i stated in the beggining)


this was a little effort , hope it helped...suggessions are invited loaded with queries

Introduction

As this is an era of web2 . so obviously there are many sources of social networking. so what i feel is the blogs are not meant only for you to exist as a web entity but also for the source of global knowledge sharing...its neither a platform for one to project himself/herself nor a communication centre (as many bloggers use to do it)..it is an interface which allows us to share what we observe,what we perceive and wats the important we think we consider.....in short here we can strenthen our power of understandings, and ability to have the closest view of the truth which one doesnt have because his/her ability to obeserve something is confined within his/her way of percepting the things...so lets harness the power of blogs in making the hunger of knowledge more intensified .....