By their very nature, pseudo code programs are not compilable and do not conform to the exact syntax of the computer language used. Since they are not compiled there is no issue with syntax errors.
When translating from pseudo code to the target computer language is when one must be careful of the syntax, but not when writing pseudo code.
There are no different TYPES as I'm aware of at all. Pseudocode is nothing in particular. It's just a way of mapping out an algorithm of some kind without going into specific details about how it will be performed in any specific programming language. The nature of how one may write down their own particular brand of psedocode is heavily based on whatever language they feel most akin to using. Pseudocode is used to convey an understanding rather than getting bogged down with any specific language so pseudocode having any FORMAL structure is just an oxymoron. It's great when you trying to convey a point to a group of programers who are all writing in different languages.
computer hacking :)
Definition:In writing and speech, the repetition of key words and phrases or the careful arrangement of words to give them special weight and prominence. Adjective: emphatic.
A way of writing computer programs that are human readable (and understandable to programmers).
It can make a big program easier to write and test. You can break the program down into individual modules that deal with a particular task. That can be tested and got to work. Then the modules can be brought together. If you know the parts were working when they were running separately it is easier to identify where a problem may be if it is not working when they are joined, than if you had written the whole program in one large block. The work can be split between different programmers if it is modularised, making better use of resources and meaning people who are particularly good at writing certain kinds of programs can be given something appropriate for them. Modules can be reused for different systems. You will find that many programs have similar elements in them, so instead of writing them every time you need it, it can be written as a module once and then used by many different programs in the future. These are just some of the advantages of using modules in programming. There are many others.
There are different ways of writing a pseudocode statement but the concept remains, it can be presented: /*Declare variables Total (number (3)) = 0 A (number (2)) =10 B (number (2)) =14 begin Total=A+B end
Be careful of extraneous words: it is called "writing" not "the writing process."
Merits: Machine language allows for direct communication with the computer hardware, resulting in very fast and efficient execution of instructions. It is also not dependent on any translator programs for execution. Demerits: Writing programs directly in machine language is very complex and error-prone, making it difficult for programmers to work with. It is also platform-dependent, meaning programs may need to be rewritten for different hardware architectures.
To explain or inform your reader about your subject. You must be careful not to confuse it with persuasive.
Writing programs in it.
There are no different TYPES as I'm aware of at all. Pseudocode is nothing in particular. It's just a way of mapping out an algorithm of some kind without going into specific details about how it will be performed in any specific programming language. The nature of how one may write down their own particular brand of psedocode is heavily based on whatever language they feel most akin to using. Pseudocode is used to convey an understanding rather than getting bogged down with any specific language so pseudocode having any FORMAL structure is just an oxymoron. It's great when you trying to convey a point to a group of programers who are all writing in different languages.
There are no different TYPES as I'm aware of at all. Pseudocode is nothing in particular. It's just a way of mapping out an algorithm of some kind without going into specific details about how it will be performed in any specific programming language. The nature of how one may write down their own particular brand of psedocode is heavily based on whatever language they feel most akin to using. Pseudocode is used to convey an understanding rather than getting bogged down with any specific language so pseudocode having any FORMAL structure is just an oxymoron. It's great when you trying to convey a point to a group of programers who are all writing in different languages.
computer hacking :)
Computer programmers write, test, and maintain the detailed instructions, called programs, that computers follow to perform their functions. Programmers also conceive, design, and test logical structures for solving problems by computer. With the help of other computer specialists, they figure out which instructions to use to make computers do specific tasks. Many technical innovations in programming-advanced computing technologies and sophisticated new languages and programming tools, for example-have redefined the role of a programmer and elevated much of the programming work done today. Job titles and descriptions may vary, depending on the organization, but computer programmers are individuals whose main job function is programming. Programmers usually write programs according to the specifications given by computer software engineers and systems analysts. (Sections on computer software engineers and on computer systems analysts appear elsewhere in the Handbook.) After engineers and analysts design software-describing how it will work-the programmer converts that design into a logical series of instructions that the computer can follow. The programmer codes these instructions in a conventional programming language such as COBOL; an artificial intelligence language such as Prolog; or one of the more advanced object-oriented languages, such as Java, C++, or ACTOR. Different programming languages are used depending on the purpose of the program. Programmers generally know more than one programming language, and because many languages are similar, they often can learn new languages relatively easily. In practice, programmers often are referred to by the language they know, such as Java programmers, or by the type of function they perform or environment in which they work-for example, database programmers, mainframe programmers, or Web programmers. Programmers also update, repair, modify, and expand existing programs. Some, especially those working on large projects that involve many programmers, use computer-assisted software engineering (CASE) tools to automate much of the coding process. These tools enable a programmer to concentrate on writing the unique parts of a program. Programmers working on smaller projects often use "programmer environments," applications that increase productivity by combining compiling, code walk through, code generation, test data generation, and debugging functions. Programmers also use libraries of basic code that can be modified or customized for a specific application. This approach yields more reliable and consistent programs and increases programmers' productivity by eliminating some routine steps. Programs vary widely depending on the type of information they will access or generate. For example, the instructions involved in updating financial records are very different from those required to simulate flight for pilot training. Simple programs can be written in a few hours, but some programs draw data from many existing systems or use complex mathematical formulas. These programs may take more than a year to create. In most cases, several programmers work together as a team under a senior programmer's supervision. Programmers test a program by running it to ensure that the instructions are correct and that the program produces the desired outcome. If errors do occur, the programmer must make the appropriate change and recheck the program until it produces the correct results. This process is called testing and debugging. Programmers may continue to fix problems for as long as a program is used. Programmers working on a mainframe, a large centralized computer, may prepare instructions for a computer operator who will run the program. (A section on computer operators appears elsewhere in the Handbook.) Programmers also may contribute to the instruction manual for a program. Programmers in software development companies may work directly with experts from various fields to create specialized software-either programs designed for specific clients or packaged software for general use-ranging from games and educational software to programs for desktop publishing and financial planning. Programming of packaged software constitutes one of the most rapidly growing segments of the computer services industry. Increasingly, advanced software platforms are bridging the gap between computer programmers and computer users. New platforms, such as spreadsheet, accounting, and enterprise resource planning applications, have created demand for computer specialists who have first-hand knowledge of a user-base. These workers use such platforms to develop programs that meet the specific needs of this base. Computer programmers often are responsible for creating the software platform, and then fine-tuning the final program after it has been made. Computer programmers often are grouped into two broad types-applications programmers and systems programmers. Applications programmers write programs to handle a specific job, such as a program to track inventory within an organization. They also may revise existing packaged software or customize generic applications purchased from vendors. Systems programmers, in contrast, write programs to maintain and control computer systems software for operating systems, networked systems, and database systems. These workers make changes in the instructions that determine how the network, workstations, and central processing unit of a system handle the various jobs they have been given, and how they communicate with peripheral equipment such as terminals, printers, and disk drives. Because of their knowledge of the entire computer system, systems programmers often help applications programmers determine the source of problems that may occur with their programs. In some organizations, workers known as programmer-analysts are responsible for both the systems analysis and programming. (A more detailed description of the work of programmer-analysts is presented in the section on computer systems analysts elsewhere in the Handbook.) Work environment. Programmers spend the majority of their time in front of a computer terminal, and work in clean, comfortable offices. Telecommuting is becoming more common, however, as technological advances allow more work to be done from remote locations. Most computer programmers work about 40 hours per week. Long hours or weekend work may be required, however, to meet deadlines or fix unexpected technical problems. About four percent work part-time, compared with about 15 percent for all occupations. Like other workers who spend long periods in front of a computer terminal typing at a keyboard, programmers are susceptible to eyestrain, back discomfort, and hand and wrist problems such as carpal tunnel syndrome. Source: U.S. Department of Labor
"There'd" is the abbreviation for "there would," but I would be careful not to use it in formal writing.
The term is diction.
It can be used for lots of programs, not just for the Web.