PLEX (programming language): Difference between revisions

Content deleted Content added
Added {{sections}} tag to article (TW)
remove {{sections|date=April 2013}}
Line 1:
 
{{sections|date=April 2013}}
{{Infobox programming language
| name = Plex
Line 27:
'''PLEX''' (''Programming Language for EXchanges'') is a special-purpose, pseudo-parallel and event-driven real-time [[programming language]]. Dedicated for [[AXE telephone exchange]]s, it was developed by Göran Hemdahl at [[Ericsson]].<ref name=ErlangHistory>{{cite web |url= http://www.cs.chalmers.se/Cs/Grundutb/Kurser/ppxt/HT2007/general/languages/armstrong-erlang_history.pdf|title= A History of Erlang|accessdate=2009-03-07 |author= Joe Armstrong|date= |work= |publisher=Ericsson AB}}</ref> Originally designed in the 1970s, it has been continuously evolving since then.<ref name=Semantics>{{cite web |url= http://cdc.ioc.ee/appsem04/webproc/short/erikson-lisper.pdf|title= A Formal Semantics for PLEX|accessdate=2009-03-07 |author= Johan Erikson and Björn Lisper|date= |work= |publisher=Mälardalen University}}</ref> The language has two variants: ''Plex-C'' used for the AXE Central Processor (CP) and ''Plex-M'' used for Extension Module Regional Processors (EMRP).<ref name=Execution>{{cite web |url= http://www.mrtc.mdh.se/publications/0802.pdf|title= The Execution Model of APZ/PLEX - An Informal Description|accessdate=2009-03-07 |author= Johan Erikson and Bo Lindell|date= |work= |publisher=Mälardalen University}}</ref>
 
==Pre-compilers==
Several [[precompiler]]s or code generators exist, to produce source code in ''Plex-C'' from [[High-level programming language|higher level]] languages or graphical models{{Citation needed|date=August 2010}}. These can generate ''Plex-C'' from:
* [[Specification and Description Language]] graphical representation (SDL/GR)
Line 35 ⟶ 36:
The binary form of ''ASA210C'' is either interpreted by a combination of hardware and microcode, or is compiled by a Just-In-Time compiler into native machine code for a high-capacity microprocessor.
 
==Features==
Code execution is triggered by specific events, encoded as signals.<ref name=Execution/>
 
An example input string that has been designed for the LI3 (P83-P90) version of the AXE Switch could be STDEP:DEV=LI3-101&&-107; this would print to the users console the current device status (busy, idle, blocked, etc.)
 
==See also==