Changes for page P@J

From version 15.1
edited by Andrea Omicini
on 31/12/2021 13:33
Change comment: There is no comment for this version
To version 12.1
edited by Andrea Omicini
on 31/12/2021 13:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +P@J
Content
... ... @@ -1,12 +1,11 @@
1 -= {{italiano}}Home di {{/italiano}}{{patj/}}{{english}} Home{{/english}} =
1 +{{velocity}}
2 +(% style='border-color:$theme.borderColor; border-style:hidden solid solid hidden' %)!!(((Although object-oriented languages are nowadays the mainstream for application development, several research contexts suggest that a multi-paradigm approach is worth pursuing. In particular, a declarative, logic-based paradigm could fruitfully add functionalities related to intelligence, adaptivity, and conciseness in expressing algorithms. The aim of the **{{patj/}}** project is to provide a framework for enhancing interoperability between Java and Prolog, based on the tuProlog open-source Prolog engine for Java.
3 +{{/velocity}}
2 2  
3 -{{include reference="Punchline" excludeFirstHeading="true"/}}
4 4  
5 -Although object-oriented languages are nowadays the mainstream for application development, several research contexts suggest that a multi-paradigm approach is worth pursuing. In particular, a declarative, logic-based paradigm could fruitfully add functionalities related to intelligence, adaptivity, and conciseness in expressing algorithms. The aim of the **{{patj/}}** project is to provide a framework for enhancing interoperability between Java and Prolog, based on the tuProlog open-source Prolog engine for Java.
6 -
7 7  P@J achieves smoother language-interoperability through two stacked layers:
8 -* an API layer for automated mapping of Java types into Prolog types (and viceversa) and seamless exploitation of the Generic Collections Framework;
9 -* an annotation layer, that aims at truly extending Java programming with the ability of specifying Prolog-based declarative implementations of Java methods, relying on Java annotations.
7 +* an API layer for automated mapping of Java types into Prolog types (and viceversa) and seamless exploitation of the Generic Collections Framework;
8 +* an annotation layer, that aims at truly extending Java programming with the ability of specifying Prolog-based declarative implementations of Java methods, relying on Java annotations.)))
10 10  
11 11  >P@J Technology
12 12  

Contacts

Mirko Viroli

2P