Opa (programming language): Difference between revisions

Revision as of 18:37, 17 August 2013

Revision as of 06:47, 22 August 2013

Line 30:

Its designers assert that this helps Opa to avoid many security issues, like [[SQL injection]]s or [[Cross-site scripting|XSS attacks]].<ref>{{cite web|url=http://www.heise.de/developer/meldung/Auch-Opa-ist-fuer-Cloud-Anwendungen-1288588.html|title=Auch Opa ist für Cloud-Anwendungen |publisher=[[Heise Online]]|date=29 July 2011}}</ref>

The core language is [[functional programming|functional]] and has a static [[type system]] with [[type inference]]. Opa also provides sessions which encapsulate an [[imperative programming|imperative]] state and communicate using [[message passing]], similar to [[Erlang (programming language)|Erlang]] processes. Opa provides many structures or functions that are common in web development, as [[first-class object]]s,

for instance [[HTML]]<ref>{{cite web|url=http://www.i-programmer.info/news/98-languages/2961-opa-a-unified-approach-to-web-programming.html

|title=Opa - a unified approach to web programming |publisher=i-Programmer |date=28 August 2011}}</ref> and [[parser]]s, based on [[Parsing Expression Grammar]]s.<ref>{{cite web |author=Koprowski, Binsztok |year=2011|url=http://www.lmcs-online.org/ojs/viewarticle.php?id=708&layout=abstract|title=TRX: A Formally Verified Parser Interpreter|publisher=Logical Methods in Computer Science |doi=10.2168}}</ref>