Computer Programming

An algorithm is a set of instructions that a computer follows, generally to accomplish one specific task. These tasks can range from sorting a set of numbers to finding the greatest common denominator of two numbers.

Variable-declaration is:

extern int x;

extern double y;

extern char a;

Variable-definition is:

int x;

static double y;

auto char a;

Variable-definition with initialization is:

int x = 1;

static double y= 2.3;

auto char a = 'w';

John Backus, who died March 17 of this year, led the team that developed Fortran at IBM in 1954.

Computer scientists and mathematicians commonly use algorithms. However, this is only in the strictest sense. An algorithm is simply a process or set of rules to be followed in problem-solving situations. If you're tired and need some coffee, you follow an algorithm to solve that problem: going to the machine, putting in grounds, putting in water, putting a cup or carafe below the spot, hitting the proper buttons, etc. Without algorithms, daily life for every person in the world would be very difficult--it would be like performing every action for the very first time.

The Recordset was not XML-based and could not be serialized to XML easily or flexibly.

Finally, a Recordset was not independent of a data store because it tracked a Connection object

and through its methods could send queries to the data source to populate, update,

and refresh its data.

To that end, the Recordset contained functionality found in the ADO.NET DataSet,

data reader, and data adapter objects.

Similar to the DataSet, a Recordset could be disconnected from its data store

and therefore act as an in-memory cache of data.

Of course, it could also be used in a connected model depending on the cursor options that were set.

Although the Recordset object stored multiple versions of each column for each of its rows,

it was not by nature able to represent multiple tables without the use of the Data Shape Provider.

//program to find the age of given date of birth

#include <dos.h>

#include <stdio.h>

int main(void)

{

struct date d;

int bd,bm,by,day,m,y,cd,cm,cy;

clrscr();

getdate(&d);

printf("\t**********WELCOME TO AGE FINDER PLACE************\n");

printf("\t*************************************************\n\n");

cd=d.da_day;

cm=d.da_mon;

cy=d.da_year;

printf("Enter the birthe date : ");

scanf("d%d",&bd,&bm,&by);

{

if(cd<bd)

{

cm=cm-1;

cd=cd+30;

day=cd-bd;

}else

day=d.da_day-bd;

}

{

if(cm<bm)

{

cy=cy-1;

cm=cm+12;

m=cm-bm;

}else

m=d.da_mon-bm;

}

y=cy-by;

printf("your age is:-\n");

printf("year=%d\tmonth=%d\tday=%d\n",y,m,day);

getch();

}

//by DILKASH

from MANUU

The organizational structure, work activities, and informational content identified in a job analysis serve as the basis for developing both the structure and content of a training program

Programmers tend to think like programmers rather than users. So while they may be capable of producing highly complex software, they may not be able to present the software in a user-friendly manner. Thus we have user interface specialists who spend a huge amount of time and vast amounts of money testing user interfaces upon users of varying degrees of ability. They can then present programmers with their findings and modify their software to provide more intuitive interfaces. Even then, they can still get it completely wrong because someone has to program the interfaces for the test subjects, thus the chosen interfaces are simply the best of what could be bad selection of interfaces. The best of the bad is still bad. So interface specialists spend even more time and money improving the test interfaces. Eventually, one hopes, they get it right and the programmer can finally create software that is intuitive.

With graphical user interfaces (GUIs) like Windows, designing interfaces becomes easier because the interface already exists, the programmer simply has to ensure his interface is consistent with those of other programs, thus making it more intuitive because users already familiar with one application's interface can use the same skills to navigate any similar interface. However, this relies on the fact the GUI is well-designed to begin with and anyone who's used Windows knows just how frustrating an interface it can be. Worse, each new version of Windows changes the interface in various ways, removing familiar features or adding new features. hopefully for the better, but not always. The removal of the start button from Windows 8 was particularly frustrating because the GUI was targeted towards touch-screen users -- which is fine unless you don't happen to have a touch-screen. so although the majority of Microsoft programmers are highly-skilled individuals, even they can get it hopelessly wrong. The software itself is of an extremely high quality, but it's not much use if users are constantly frustrated by the inadequacies of the interface. However it would unfair to blame the programmers for a poor interface -- the user-interface specialists are the ones giving the least value for money. But it is money that has to be spent if an interface is to improve.

A constructor is not a mandatory member that we need to code specifically for a class. While creating a class, even if we miss out coding the constructor, Java would create a default constructor all by itself.

The constructor is usually the place where we initialize things that are required by the class. Hence it is a good practice to code the constructor for our class.

Tip: If you do not want anyone to instantiate your class, you can declare the constructor as private. In that way no other class can instantiate your class.

#include<iostream.h>

#include<stdlib.h>

#include<conio.h>

struct poly

{

int coeff;

int x;

int y;

int z;

struct poly * next;

};

class polynomial

{

private :

poly *head;

public:

polynomial():head(NULL)

{

}

void getdata();

void display();

void insert(poly *prv,poly *curr,poly *p);

polynomial operator + (polynomial );

};

polynomial polynomial :: operator +(polynomial px2)

{

polynomial px;

poly *t1,*t2,*t3,*last;

t1 = head;

t2 = px2.head;

px.head = NULL;

while(t1 != NULL && t2 != NULL)

{

t3 = new poly;

t3->next = NULL;

if(t1->x NULL)

{

head->next = node;

node->next = NULL;

}

else

insert(head,head->next,node);

}

}

void polynomial :: display()

{

poly *temp;

temp = head;

cout << endl << "Polynomial :: ";

while(temp != NULL)

{

if(temp->coeff < 0)

cout << " - ";

cout << abs(temp->coeff);

if(temp->x != 0)

cout << "x^" << temp->x;

if(temp->y != 0)

cout << "y^" << temp->y;

if(temp->z != 0)

cout << "z^" << temp->z;

if(temp->next->coeff > 0)

cout << " + ";

temp = temp->next;

}

cout << " = 0";

}

void main()

{

polynomial px1,px2,px3;

clrscr();

px1.getdata();

px2.getdata();

px3 = px1 + px2;

px1.display();

px2.display();

px3.display();

getch();

}

Identifiers or symbols are the names you supply for variables,type,function and labels.Identifiers names must differ in spelling and case from any keyword.you cannot use keyword as an identifier.you can create an identifier by specifying it in the declaration of a variable,type or function.

Hexadecimal numbers can be manipulated in exactly the same was as decimal. The digits we can use are: 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. Let us take two numbers, say, 7 and 6. In decimal, we can count from 7 upward by 6... 8, 9, 10, 11, 12, 13. In Hexadecimal, we can do the same... 8, 9, A, B, C, D. Let's take two more numbers, D and 4. We count upwards from D by 4... E, F, 10, 11. Notice that after F, there is no other digit we can use, to we carry 1 to the 16's column and carry on counting to reach the final figure of 11Hex. This is just the same as the decimal procedure of carrying to the tens column after we pass 9. Once you have got your head around the idea of extra digits, the rest of it is as easy as decimal.

The aim of all computer languages is to make it easier for humans to create and modify machine code, the native language of the machine.

Data processing is basically the transformation of raw data to import data through a procedure. Data is controlled to create results that lead to the goals of an issue or improvement of a current circumstance. Methods of data processing:-

1. Manual Data Processing, Data is processed manually without using any machine or tools to get the required result.
2. Mechanical Data Processing, Data is processed using different devices like a typewriter, mechanical printers, and other devices.
3. Electronic Data Processing, Data is processed through a computer; data & set of instructions are given to the computer as input, and computer-processed data according to given instruction.
   · Batch processing · Online processing · Distributed processing · Real-time processing

The first tractors were steam powered vehicles in the 1860s.

Starting from the centre, move forward 100 pixels, turn 180 degrees and move forward 100 pixels (returning to the centre). Then turn 120 degrees. Repeat three times.

repeat 3 [fd 100 rt 180 fd 100 lt 120]

I would recommend that you A) develop and understanding of HTML and B) learn javascript. It is a very easy language and there are a plethora of examples and good explanations of how to write it. Visual basic is a good language to learn as well, but with javascript all you need is a text editor and a web browser and you can practice on any computer.

When the code is targeted towards a specific machine architecture. Machine code is entirely machine-dependent, as is the low-level assembly language used to produce that machine code. High-level languages are not machine dependant, however source code can still be targeted towards a specific architecture or platform. Such code is non-portable, however many high-level languages provide methods to filter machine-dependant or platform-dependant code such that the same source code can be compiled on different machines and platforms.

Network protocols allows computers to speak with each other. The most common protocol used today is TCP/IP, or the Transmission Control Protocol/Internet Protocol suite. Other protocols are still in use but are in fairly rapid decline as more devices and software standardize themselves to Internet connectivity.

Oh my god, have you been reading my old books? Forget COBOL learn C++. What is this a nostagia in old computer languages. Next, I'll be answering questions about Fortran. Learn Linux while you're at it, it's a throwback to Unix and does anybody remember BASIC? or should we just go back to the Dead Sea Scrolls?

No. Optical storage is something that can be read using the aid of light. So CD's, DVD's would be examples of optical storage.

Spinning hard drives are not optical either. They use magnetism to store data.