2-APL UPC project.
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

bbfizp 34067233 070d1761

+4 -4
+4 -4
docs/briscola_chiamata/bc-doc.tex
··· 272 272 273 273 \section{Conclusion}\label{sec:concl} 274 274 275 - The general feeling after implementing the Briscola Chiamta game into the 2APL system is both good and bad. We will start with the positive aspects. 275 + The general feeling after implementing the briscola game into the 2APL system is both good and bad. I will start with the positive aspects. 276 276 277 277 Having a declarative programming when developing agents certainly gives the designer more freedom and a certain level of confidence that you would not have with other languages. You can focus specifically on 'what' you want your agents to do and not 'how'. This conceptual division is one of the main attractions of 2APL and even though some of us required to learn this type of programming in more depth as we had no previous experience in it, we certainly appreciated the benefit gained when we were in the implementation stage. 278 278 279 279 The JADE platform tools and some of 2APL tools were certainly helpful from beginning to end and provided us with information that would have otherwise been hard to see or find. Of course we can connect any of our agents to any other agent in the JADE platform and having portability is a helpful and important feature. 280 280 281 - The negative aspects of 2APL are few, but certainly big. Firstly it is clearly a tool for research and not for real development. The documentation for 2APL has been ignored by its developers for far too long, it is simplistic , undetailed and the examples shown are ...one (which is not even fully explained!).The environment we built was done by scanning the code of some of the Java classes of an example and thus we lacked the true ability to implement a full application (this was never our intention, but knowing that if you wanted it would be very difficult certainly isn't a positive aspect). 281 + The negative aspects of 2APL are few, but certainly relevant. Firstly it is clearly a tool designed primarily for research and not for market development. The documentation for 2APL is still relatively vague and requires some updating, while the examples given are few and sadly not fully detailed.The environment we built was done by scanning the code of some of the java classes of an example and thus we lacked the true ability to implement a full application (this was never our intention, but knowing that if you wanted it would be very difficult certainly isnt a positive aspect). 282 282 283 - Even though prolog does give us a very powerful logic system, it does lack other tools such as databases, load data and other form of operation in which a prolog library would be required (and not allowed in 2APL). Finally, even though it was previously mentioned, the 2APL parser was so unhelpful that it barely provided us with any useful information. Clearer instructions or error messages would be necessary if any serious development was to be made in this language. 283 + Even though prolog does give us a very powerful logic system, it does lack other tools such as databases, load data and other form of operation in which a prolog library would be required (and not allowed in 2APL).Finally, even though it was previously mentioned, the 2APL parser was so unhelpful that it barely provided us with any useful information. Clearer instructions or error messages would be necessary if any serious development was to be made in this language. 284 284 285 - So even though we praised 2APL for some things and despised it for others, as a whole we were pleased to develop with 2APL and do believe that with more work it can become the "go to" language of multi agent systems... at least from a research point of view. 285 + So even though we praised 2APL for some things and despised it for others, as a whole we were pleased to develop with 2APL and do believe that with more work it can become the "go to" language of multiagent systems... at least from a research point of view. 286 286 287 287 288 288 \section{Bibliography}