What is PRO­GRAM­MING PARADIGM? What does PRO­GRAM­MING PARADIGM mean?

• Re­port rights in­fringe­ment
• pub­lished: 29 Aug 2016
• views: 529

What is PRO­GRAM­MING PARADIGM? What does PRO­GRAM­MING PARADIGM mean? PRO­GRAM­MING PARADIGM mean­ing - PRO­GRAM­MING PARADIGM def­i­ni­tion - PRO­GRAM­MING PARADIGM ex­pla­na­tion. Source: Wikipedia.org ar­ti­cle, adapt­ed under https://​creativecommons.​org/​licenses/​by-sa/​3.0/ li­cense. In com­put­er pro­gram­ming, the no­tion of pro­gram­ming paradigms can have some­what dif­fer­ent mean­ings de­pend­ing on its con­text of use. In­volv­ing pro­gram­ming lan­guages and pro­gram­ming: it is a way to clas­si­fy pro­gram­ming lan­guages ac­cord­ing to the style of com­put­er pro­gram­ming and id­ioms used. In­volv­ing soft­ware de­vel­op­ment: it is a fun­da­men­tal style of pro­gram­ming, which is not gen­er­al­ly dic­tat­ed by the pro­ject man­age­ment method­ol­o­gy (such as wa­ter­fall or agile). Paradigms dif­fer in the con­cepts and ab­strac­tions used to rep­re­sent the el­e­ments of a pro­gram (such as ob­jects, func­tions, vari­ables, con­straints) and the steps that com­prise a com­pu­ta­tion (such as assig­na­tions, eval­u­a­tion, con­tin­u­a­tions, data flows) Fea­tures of var­i­ous pro­gram­ming lan­guages de­ter­mine which paradigms they be­long to. Thus, some lan­guages fall into only one paradigm, while oth­ers fall into mul­ti­ple paradigms. Some paradigms are con­cerned main­ly with im­pli­ca­tions for the ex­e­cu­tion model of the lan­guage, such as al­low­ing side ef­fects, or whether the se­quence of op­er­a­tions is de­fined by the ex­e­cu­tion model. Other paradigms are con­cerned main­ly with the way code is or­ga­nized, such as group­ing code into units along with the state that is mod­i­fied by the code. Yet oth­ers are con­cerned main­ly with the style of syn­tax and gram­mar. Com­mon pro­gram­ming paradigms in­clude im­per­a­tive which al­lows side ef­fects, func­tion­al which does not allow side ef­fects, declar­a­tive which does not state the order in which op­er­a­tions ex­e­cute, ob­ject-ori­ent­ed which groups code to­geth­er with the state the code mod­i­fies, pro­ce­du­ral which groups code into func­tions, logic which has a spe­cif­ic style of ex­e­cu­tion model cou­pled to a spe­cif­ic style of syn­tax and gram­mar, and sym­bol­ic pro­gram­ming which has a spe­cif­ic style of syn­tax and gram­mar. For ex­am­ple, lan­guages that fall into the im­per­a­tive paradigm have two main fea­tures: they state the order in which op­er­a­tions take place, with con­structs that ex­plic­it­ly con­trol that order, and they allow side ef­fects, in which state can be mod­i­fied at one point in time, with­in one unit of code, and then later read at a dif­fer­ent point in time in­side a dif­fer­ent unit of code. The com­mu­ni­ca­tion be­tween the units of code is not ex­plic­it. Mean­while, in ob­ject-ori­ent­ed pro­gram­ming, code is or­ga­nized into ob­jects that con­tain state that is only mod­i­fied by the code that is part of the ob­ject. Most ob­ject ori­ent­ed lan­guages are also im­per­a­tive lan­guages. In con­trast, lan­guages that fit the declar­a­tive paradigm do not state the order in which to ex­e­cute op­er­a­tions. In­stead, they sup­ply a num­ber of op­er­a­tions that are avail­able in the sys­tem, along with the con­di­tions under which each is al­lowed to ex­e­cute. The im­ple­men­ta­tion of the lan­guage's ex­e­cu­tion model tracks which op­er­a­tions are free to ex­e­cute and choos­es the order on its own.

What is PRO­GRAM­MING PARADIGM? What does PRO­GRAM­MING PARADIGM mean?

• Re­port rights in­fringe­ment
• pub­lished: 29 Aug 2016
• views: 529

What is PRO­GRAM­MING PARADIGM? What does PRO­GRAM­MING PARADIGM mean? PRO­GRAM­MING PARADIGM mean­ing - PRO­GRAM­MING PARADIGM def­i­ni­tion - PRO­GRAM­MING PARADIGM ex­pla­na­tion. Source: Wikipedia.org ar­ti­cle, adapt­ed under https://​creativecommons.​org/​licenses/​by-sa/​3.0/ li­cense. In com­put­er pro­gram­ming, the no­tion of pro­gram­ming paradigms can have some­what dif­fer­ent mean­ings de­pend­ing on its con­text of use. In­volv­ing pro­gram­ming lan­guages and pro­gram­ming: it is a way to clas­si­fy pro­gram­ming lan­guages ac­cord­ing to the style of com­put­er pro­gram­ming and id­ioms used. In­volv­ing soft­ware de­vel­op­ment: it is a fun­da­men­tal style of pro­gram­ming, which is not gen­er­al­ly dic­tat­ed by the pro­ject man­age­ment method­ol­o­gy (such as wa­ter­fall or agile). Paradigms dif­fer in the con­cepts and ab­strac­tions used to rep­re­sent the el­e­ments of a pro­gram (such as ob­jects, func­tions, vari­ables, con­straints) and the steps that com­prise a com­pu­ta­tion (such as assig­na­tions, eval­u­a­tion, con­tin­u­a­tions, data flows) Fea­tures of var­i­ous pro­gram­ming lan­guages de­ter­mine which paradigms they be­long to. Thus, some lan­guages fall into only one paradigm, while oth­ers fall into mul­ti­ple paradigms. Some paradigms are con­cerned main­ly with im­pli­ca­tions for the ex­e­cu­tion model of the lan­guage, such as al­low­ing side ef­fects, or whether the se­quence of op­er­a­tions is de­fined by the ex­e­cu­tion model. Other paradigms are con­cerned main­ly with the way code is or­ga­nized, such as group­ing code into units along with the state that is mod­i­fied by the code. Yet oth­ers are con­cerned main­ly with the style of syn­tax and gram­mar. Com­mon pro­gram­ming paradigms in­clude im­per­a­tive which al­lows side ef­fects, func­tion­al which does not allow side ef­fects, declar­a­tive which does not state the order in which op­er­a­tions ex­e­cute, ob­ject-ori­ent­ed which groups code to­geth­er with the state the code mod­i­fies, pro­ce­du­ral which groups code into func­tions, logic which has a spe­cif­ic style of ex­e­cu­tion model cou­pled to a spe­cif­ic style of syn­tax and gram­mar, and sym­bol­ic pro­gram­ming which has a spe­cif­ic style of syn­tax and gram­mar. For ex­am­ple, lan­guages that fall into the im­per­a­tive paradigm have two main fea­tures: they state the order in which op­er­a­tions take place, with con­structs that ex­plic­it­ly con­trol that order, and they allow side ef­fects, in which state can be mod­i­fied at one point in time, with­in one unit of code, and then later read at a dif­fer­ent point in time in­side a dif­fer­ent unit of code. The com­mu­ni­ca­tion be­tween the units of code is not ex­plic­it. Mean­while, in ob­ject-ori­ent­ed pro­gram­ming, code is or­ga­nized into ob­jects that con­tain state that is only mod­i­fied by the code that is part of the ob­ject. Most ob­ject ori­ent­ed lan­guages are also im­per­a­tive lan­guages. In con­trast, lan­guages that fit the declar­a­tive paradigm do not state the order in which to ex­e­cute op­er­a­tions. In­stead, they sup­ply a num­ber of op­er­a­tions that are avail­able in the sys­tem, along with the con­di­tions under which each is al­lowed to ex­e­cute. The im­ple­men­ta­tion of the lan­guage's ex­e­cu­tion model tracks which op­er­a­tions are free to ex­e­cute and choos­es the order on its own.