Diclib.com
Wörterbuch ChatGPT

Wörterbuchsuche Kundenspezifische Lösungen

Geben Sie ein Wort oder eine Phrase in einer beliebigen Sprache ein 👆

Sprache:

Übersetzung und Analyse von Wörtern durch künstliche Intelligenz ChatGPT

Auf dieser Seite erhalten Sie eine detaillierte Analyse eines Wortes oder einer Phrase mithilfe der besten heute verfügbaren Technologie der künstlichen Intelligenz:

wie das Wort verwendet wird
Häufigkeit der Nutzung
es wird häufiger in mündlicher oder schriftlicher Rede verwendet
Wortübersetzungsoptionen
Anwendungsbeispiele (mehrere Phrasen mit Übersetzung)
Etymologie

Was (wer) ist Ousterhout's dichotomy - definition

DIVISION OF PROGRAMMING LANGUAGES INTO SYSTEM PROGRAMMING AND SCRIPTING

Ousterhout's dichotomy

<language> John Ousterhout's division of {high-level languages} into "system programming languages" and "scripting languages". This distinction underlies the design of his language Tcl. System programming languages (or "applications languages") are strongly typed, allow arbitrarily complex data structures, and programs in them are compiled, and are meant to operate largely independently of other programs. Prototypical system programming languages are C and Modula-2. By contrast, scripting languages (or "glue languages") are weakly typed or untyped, have little or no provision for complex data structures, and programs in them ("scripts") are interpreted. Scripts need to interact either with other programs (often as glue) or with a set of functions provided by the interpreter, as with the file system functions provided in a UNIX shell and with Tcl's GUI functions. Prototypical scripting languages are AppleScript, C Shell, MS-DOS batch files and Tcl. Many believe that this is a highly arbitrary dichotomy, and refer to it as "Ousterhout's fallacy" or "Ousterhout's false dichotomy". While strong-versus-weak typing, data structure complexity, and independent versus stand-alone might be said to be unrelated features, the usual critique of Ousterhout's dichotomy is of its distinction of compilation versus interpretation, since neither semantics nor syntax depend significantly on whether code is compiled into machine-language, interpreted, tokenized, or byte-compiled at the start of each run, or any mixture of these. Many languages fall between being interpreted or compiled (e.g. Lisp, Forth, UCSD Pascal, Perl, and Java). This makes compilation versus interpretation a dubious parameter in a taxonomy of programming languages. (2002-05-28)

Kraepelinian dichotomy

DIVISION

User:FiachraByrne/Kraepelinian dichotomy; Kraepelin dichotomy; Kraepelin's dichotomy

The Kraepelinian dichotomy is the division of the major endogenous psychoses into the disease concepts of dementia praecox, which was reformulated as schizophrenia by Eugen Bleuler by 1908,; and manic-depressive psychosis, which has now been reconceived as bipolar disorder. This division was formally introduced in the sixth edition of Emil Kraepelin's psychiatric textbook Psychiatrie.

https://en.wikipedia.org/wiki/Kraepelinian_dichotomy

Classical dichotomy

THE IDEA, ATTRIBUTED TO CLASSICAL/PRE-KEYNESIAN ECONOMICS, THAT REAL VARIABLES (OUTPUT AND REAL INTEREST RATES) AND NOMINAL VARIABLES (MONEY VALUE OF OUTPUT AND THE INTEREST RATE) CAN BE ANALYZED SEPARATELY

Dichotomous market theory

In macroeconomics, the classical dichotomy is the idea, attributed to classical and pre-Keynesian economics, that real and nominal variables can be analyzed separately. To be precise, an economy exhibits the classical dichotomy if real variables such as output and real interest rates can be completely analyzed without considering what is happening to their nominal counterparts, the money value of output and the interest rate.

https://en.wikipedia.org/wiki/Classical_dichotomy

Wikipedia

Ousterhout's dichotomy

Ousterhout's dichotomy is computer scientist John Ousterhout's categorization that high-level programming languages tend to fall into two groups, each with distinct properties and uses: system programming languages and scripting languages – compare programming in the large and programming in the small. This distinction underlies the design of his language Tcl.

System programming languages (or applications languages) usually have the following properties:

They are typed statically
They support creating complex data structures
Programs in them are compiled into machine code
Programs in them are meant to operate largely independently of other programs

System programming languages tend to be used for components and applications with large amounts of internal functionality such as operating systems, database servers, and Web browsers. These applications typically employ complex algorithms and data structures and require high performance. Prototypical examples of system programming languages include C, OCaml and Modula-2.

By contrast, scripting languages (or glue languages) tend to have the following properties:

They are typed dynamically
They have little or no provision for complex data structures
Programs in them (scripts) are interpreted

Scripting languages tend to be used for applications where most of the functionality comes from other programs (often implemented in system programming languages); the scripts are used to glue together other programs or add additional layers of functionality on top of existing programs. Ousterhout claims that scripts tend to be short and are often written by less sophisticated programmers, so execution efficiency is less important than simplicity and ease of interaction with other programs. Common applications for scripting include Web page generation, report generation, graphical user interfaces, and system administration. Prototypical examples of scripting languages include Python, AppleScript, C shell, DOS batch files, and Tcl.

https://en.wikipedia.org/wiki/Ousterhout's dichotomy