jason-users Mailing List for jason

Hi, we improved the document describing how to run Jason application with
Gradle

https://github.com/jason-lang/jason/blob/master/doc/tutorials/getting-started/shell-based.adoc#with-gradle

It manages dependencies and versions far better than other options and does
not requires that the user downloads Jason. Eclipse projects can be created
by "Import Gradle Project".

Jomi

Hi Stephen, for sure this new syntax have to be included in the plugin… I likely missed to inform the plugin developer (Maicon Zatelli, in CC) these changes. 

The suggested internal action is included in the GitHub / local maven repository.

Best,

Jomi

ps.: you can always run projects with the new syntax using gradle or shell commands. 

> On 18 Nov 2018, at 19:53, Stephen Cranefield <ste...@ot...> wrote:
> 
> I would like to be able to use the version 2.2 syntax extensions ('@#AtomInSingleQuotes' and elif clauses in if-then-else statements) with the Eclipse plugin. However, Eclipse considers these as errors and will not let me run any code that uses themt.
> 
> I have the latest Jason-2.4 snapshot jar in the Java Build Path in my project properties. Do I need to anything else to get the Eclipse extension to use an up-to-date parser? I am using Eclipse 2018-09 (4.9.0) and version 1.0.21.201704271508 of the Jasonide_feature.
> 
> By the way, it would be useful to have a .version(V) internal action, so users can be sure what version of Jason they are running.
> 
> Regards,
> Stephen
> 
> 
> _______________________________________________
> Jason-users mailing list
> Jas...@li...
> https://lists.sourceforge.net/lists/listinfo/jason-users

I would like to be able to use the version 2.2 syntax extensions ('@#AtomInSingleQuotes' and elif clauses in if-then-else statements) with the Eclipse plugin. However, Eclipse considers these as errors and will not let me run any code that uses themt.

I have the latest Jason-2.4 snapshot jar in the Java Build Path in my project properties. Do I need to anything else to get the Eclipse extension to use an up-to-date parser? I am using Eclipse 2018-09 (4.9.0) and version 1.0.21.201704271508 of the Jasonide_feature.

By the way, it would be useful to have a .version(V) internal action, so users can be sure what version of Jason they are running.

Regards,
Stephen

Hi Stephen,

thanks for reporting the problem, as Rafael said, it is a bug! 

I fixed it and committed in the github.

Best,

Jomi

p.s.: in case you want to get it from a maven repository:
	http://jacamo.sourceforge.net/maven2/org/jason-lang/jason/2.4-SNAPSHOT/


> On 31 Oct 2018, at 00:52, Stephen Cranefield <ste...@ot...> wrote:
> 
> The following asl code fails to compile in Jason 2.3:
> 
> @foo(1)
> +!g <- .print("Plan ", foo(1), " was called").
> 
> @foo(2)
> +!g <- .print("Plan ", foo(2), " was called").
> 
> I get this exception:
> 
> [test_plan_labels] as2j: error parsing "<...>\test_plan_labels.asl"
> jason.JasonException: There already is a plan with label foo(2)
> 	at jason.asSyntax.PlanLibrary.add(PlanLibrary.java:152)
> 	at jason.asSyntax.PlanLibrary.add(PlanLibrary.java:128)
> 	at jason.asSyntax.parser.as2j.agent(as2j.java:215)
> 	at jason.asSemantics.Agent.parseAS(Agent.java:419)
> 	at jason.asSemantics.Agent.parseAS(Agent.java:404)
> 	at jason.asSemantics.Agent.load(Agent.java:174)
> 	at jason.asSemantics.Agent.create(Agent.java:121)
> 	at jason.infra.centralised.CentralisedAgArch.createArchs(CentralisedAgArch.java:72)
> 	at jason.infra.centralised.RunCentralisedMAS.createAgs(RunCentralisedMAS.java:481)
> 	at jason.infra.centralised.RunCentralisedMAS.create(RunCentralisedMAS.java:202)
> 	at jason.infra.centralised.RunCentralisedMAS.main(RunCentralisedMAS.java:79)
> 
> I read on page 58 of the Jason book that "as a label, it is normal practice to use a predicate of arity 0". However, the earlier part of that sentence says "we can use a complex predicate", and the example shown at the top of that page has this label: @shopping(1)[chance_of_success(0.7),usual_payoff(0.9), source(ag1),expires(autumn)]. The book does not say that when a plan label's arity is greater than 0, there must only be one instance of a plan label with the label's functor, so I presume that the exception above is due to a bug, not the code being in error.
> 
> Regards,
> Stephen
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Jason-users mailing list
> Jas...@li...
> https://lists.sourceforge.net/lists/listinfo/jason-users

-- 
Jomi Fred Hubner
Department of Automation and Systems Engineering
Federal University of Santa Catarina
PO Box 476, Florianópolis, SC
88040-900 Brazil
http://jomi.das.ufsc.br
-- 
be good. be kind. be happy. (Conrad Anker)