Content deleted Content added
→top: remove editorializing |
[{"MMS":{"_id":"1","thread_id":"3","date":"1704082775","date_sent":"170 4082775","msg_box":"1","read":"1","m_id":"7dea52d0-c02f-4c32-859c-c5002 135b06a","sub":"","sub_cs":"106","ct_t":"text\/plain","m_type":"132","m _size":"0","tr_id":"proto:Co4BCiJjb20uZ29vZ2xlLmFuZHJvaWQuYXBwcy5tZXNzY WdpbmcuEmgSZho+CiJ0ZWxjZWwtYWRlbGFudGEtbWVnYXMtcmNzQHJibS5nb29nEg9BZGVs YW50YSBUZWxjZWwaByMzNzQ3NEYqJDdkZWE1MmQwLWMwMmYtNGMzMi04NTljLWM1MDAyMTM 1YjA2YQ==","ct_cls":"135","locked":"0","sub_id":"1","seen":"1","crea Tags: Reverted Visual edit Mobile edit Mobile web edit |
||
Line 11:
What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For example, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.
In [[parallel computing]], the execution model often
| url = http://compss.bsc.es/
| title = COMP Superscalar Programming Model
|