jason-users Mailing List for jason

maybe, you can use some meta-programming with =.. operator
...
.intend(G) &
G =.. [Functor,[Arg1,Arg2],Annots] & // G arity is 2
.fail_goal(G) & ....


On Fri, 26 Apr 2019 at 12:00, Jomi Hubner <jom...@gm...> wrote:

> Hi Amandine,
>
> yes, vars can have annotations, but not terms. Using other words, the
> functor can be a variable (for unification purposes).
>
> Jomi
>
> > On 26 Apr 2019, at 10:25, Amandine Mayima <am...@la...> wrote:
> >
> > Hello,
> >
> > Is it normal that beliefs in the form of Var can be added but not in the
> form of Var(atom/Var) which are parsed when belief addition as +Var;
> atom/Var; ? When it's Var(atom1/Var2,atom2/Var3), it cannot be parsed. From
> the EBNF, I understand that it should be possible.
> >
> > Of the same style, I cannot use an IA with an argument of the form
> Var(atom/Var) for example I can do .fail_goal(goto(Place,Speed)), I can do
> .fail_goal(TaskName) but I cannot do .fail_goal(TaskName(Place,Speed)).
> >
> > Best regards,
> >
> > Amandine
> >
> >
> >
> > _______________________________________________
> > 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)
>
>
>
>

Hi Amandine,

yes, vars can have annotations, but not terms. Using other words, the functor can be a variable (for unification purposes).

Jomi

> On 26 Apr 2019, at 10:25, Amandine Mayima <am...@la...> wrote:
> 
> Hello,
> 
> Is it normal that beliefs in the form of Var can be added but not in the form of Var(atom/Var) which are parsed when belief addition as +Var; atom/Var; ? When it's Var(atom1/Var2,atom2/Var3), it cannot be parsed. From the EBNF, I understand that it should be possible.
> 
> Of the same style, I cannot use an IA with an argument of the form Var(atom/Var) for example I can do .fail_goal(goto(Place,Speed)), I can do .fail_goal(TaskName) but I cannot do .fail_goal(TaskName(Place,Speed)).
> 
> Best regards,
> 
> Amandine
> 
> 
> 
> _______________________________________________
> 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)

Hello,

Is it normal that beliefs in the form of Var can be added but not in the 
form of Var(atom/Var) which are parsed when belief addition as +Var; 
atom/Var; ? When it's Var(atom1/Var2,atom2/Var3), it cannot be parsed. 
 From the EBNF, I understand that it should be possible.

Of the same style, I cannot use an IA with an argument of the form 
Var(atom/Var) for example I can do .fail_goal(goto(Place,Speed)), I can 
do .fail_goal(TaskName) but I cannot do .fail_goal(TaskName(Place,Speed)).

Best regards,

Amandine

Thanks Amandine for the careful analysis of this bug!

I’ve just committed the fix at github.

> On 25 Apr 2019, at 07:58, Amandine Mayima <am...@la...> wrote:
> 
> Hello,
> 
> I wanted to use the internal action .abolish with vars in the annotations. It took me a while to understand why it worked with one var but not several ones : in the function hasSubsetAnnot of the class Pred, the pAnnots iterator is not reset for the second var because of the i2reset variable which had been set to true with the first var (line 361). When I remove the condition !i2reset, it works as I want to.
> 
> Example :
> 
> BB : b(a)[annot1,annot2,source(self)] ; c(d)[annot1,source(self)]
> 
> .abolish(_[annot1,annot2]) => b(a) is removed
> .abolish(_[Z]) (with Z=annot1) => c(d) is removed
> .abolish(_[annot1,Y]) (with Y=annot2) => b(a) is removed
> .abolish(_[Z,Y]) => b(a) is NOT removed because for 2 reasons I think : 1. for the second annotation Y, annot.isVar() && !i2Reset == false and 2. the alphabet order. What happens : it compares annot1 and Z, its doesn't unify, annot1 is removed from pAnnots, then it compared annot2 and Z, it unifies. Then Y is the new annot to be compared with but only source is left in i2 that has not been reset.
> 
> Best regards,
> 
> Amandine
> 
> 
> 
> _______________________________________________
> 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)

Hello,

I wanted to use the internal action .abolish with vars in the 
annotations. It took me a while to understand why it worked with one var 
but not several ones : in the function hasSubsetAnnot of the class Pred, 
the pAnnots iterator is not reset for the second var because of the 
i2reset variable which had been set to true with the first var (line 
361). When I remove the condition !i2reset, it works as I want to.

Example :

BB : b(a)[annot1,annot2,source(self)] ; c(d)[annot1,source(self)]

.abolish(_[annot1,annot2]) => b(a) is removed
.abolish(_[Z]) (with Z=annot1) => c(d) is removed
.abolish(_[annot1,Y]) (with Y=annot2) => b(a) is removed
.abolish(_[Z,Y]) => b(a) is NOT removed because for 2 reasons I think : 
1. for the second annotation Y, annot.isVar() && !i2Reset == false and 
2. the alphabet order. What happens : it compares annot1 and Z, its 
doesn't unify, annot1 is removed from pAnnots, then it compared annot2 
and Z, it unifies. Then Y is the new annot to be compared with but only 
source is left in i2 that has not been reset.

Best regards,

Amandine