Difference between revisions of "Read-eval-print loop"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
As stated in Wikipedia's explanation on [[wikipedia:Read-eval-print loop|Read-evaly-print loop]], (abbreviated as [[wikipedia:Read-eval-print loop|REPL]]) is also known as [[language shell]] or [[interactive toplevel]]. It is a technical realization of [[Hoare Triple]] in the arena of interactive programming tools. This can be directly mapped to the request-response loop in HTTP communication. Therefore, [[PKC]] will leverage this pervasive programming pattern to manage various APIs, runtime environments, and third-party software libraries. | As stated in Wikipedia's explanation on [[wikipedia:Read-eval-print loop|Read-evaly-print loop]], (abbreviated as [[wikipedia:Read-eval-print loop|REPL]]) is also known as [[language shell]] or [[interactive toplevel]]. It is a technical realization of [[Hoare Triple]] in the arena of interactive programming tools. This can be directly mapped to the request-response loop in HTTP communication. Therefore, [[PKC]] will leverage this pervasive programming pattern to manage various APIs, runtime environments, and third-party software libraries. | ||
{{category_csd=REPL,Shell,Hoare Triple | {{PagePostfix | ||
|category_csd=REPL,Shell,Hoare Triple | |||
}} | }} | ||
Revision as of 06:38, 24 November 2022
As stated in Wikipedia's explanation on Read-evaly-print loop, (abbreviated as REPL) is also known as language shell or interactive toplevel. It is a technical realization of Hoare Triple in the arena of interactive programming tools. This can be directly mapped to the request-response loop in HTTP communication. Therefore, PKC will leverage this pervasive programming pattern to manage various APIs, runtime environments, and third-party software libraries.
References