Mark,
Thanks, I'll be looking forward to the new build. The
other problem that I ran into is with the use of line
breaks.
This works:
s : String()
eval (s.startsWith("Hello") || s.startsWith("Hi"))
* drools gives an error message, but it doesn't seem
to effect anything.
This doesn't work:
s : String()
eval (s.startsWith("Hello")
|| s.startsWith("Hi"))
This is mainly for being able to format the rules
nicely. The expression can easiely get over 80
characters.
I also tried this with no luck
s : String()
eval (s.startsWith("Hello"))
or eval(s.startsWith("Hi"))
There's a similar issue in jira, but I am not sure
they are exactly the same, so decided to post it here.
--- Mark Proctor <[EMAIL PROTECTED]> wrote:
> yeah someone brought that up earlier - thank god for
> end user testing :)
> Its not an easy one to fix. It may not make it in
> for the RC release -
> we'll try our best. It will certainly be fixed
> before end of next week.
>
> Mark
> Yuesong Wang wrote:
> > 3.0 beta 3 doesn't seem to allow null as a
> constraint.
> >
> > If I do
> >
> > Cheese (type == null)
> >
> > It complains that null is not a declaration.
> >
> > Is that right?
> >
> > Thanks,
> >
> > Yuesong
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> >
> >
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
