Re: method call in expressions pb

Very very probably, it means that your resolver is defined in such a way 
that YourDVResolver.getTypeName("all") returns non-null, telling JEL that 
there is a dynamic variable named "all".

Once you have both dynamic variable and method with the same name in the 
namespace, the dynamic variable resolution takes a priority. Thus, "all" 
is a dynamic variable to JEL and it can't have formal parameters.

If this scheme of namespace conflict resolution is undesirable, You will 
need to ensure that there are no conflicts between the library and the 
dynamic variables.

With the best regards,
                           Konstantin.


On Mon, 16 May 2005, damien benoist wrote:

> Hello,
>
> I have a list of dynamic variables.
> Those variables are boolean and have a name (String).
> I would like to add a function which returns true
> if all the variables matching a regexp are true:
>
>       all("dum*")
>
> When compiling the expression, i get the following
> exception:
>
>       gnu.jel.CompilationException:
> Dynamic variable cant have the formal parameters.
>
> I've set a dynamic lib with an "all" method:
>
> public boolean                  all(
> String                          reStr) {
>
>    ...
> }
>
> What am i doing wrong (again)?
>
> Thanks for your help.
>
>
>
>
> Yahoo! Mail
> Stay connected, organized, and protected. Take the tour:
> http://tour.mail.yahoo.com/mailtour.html
>
>
>
> _______________________________________________
> Help-jel mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/help-jel
>