Forget the "pre-processor flag". You can't convert '#' to
'//' safely without
proper parsing: just think of '#' after '//' or '#' between
'/*' and '*/',
'#' inside '"' and '"'.
I think that it'll also have some repercussions in template expansion.
The DSL parser is also using '#' and '//'. Some change in the code might
be required, too.
-W
On 06/02/2012, Mark Proctor <mproctor(a)codehaus.org> wrote:
tbh it should have been removed ages ago, it's showing some bit
rot
there, I thought it had been an "internal undocumented" feature for a
while :)
Could you submit a pull request that expunges it completely?
We need the # character for inline casting and coercion. We'll probably
add a pre-processor flag to mass convert # to // for backwards
compatability.
Mark
On 06/02/2012 16:52, Wolfgang Laun wrote:
> (Why this sudden return to orthogonality?)
>
> Expert still shows the diagram for "comment" with a '#' as the
first
> choice:
> images/Chapter-Rule_Language/single_line_comment.png
>
> Also, the warning contains a typo:
> <para>Drools also suppors for backward compatibility
>
> s/suppors/supports/
>
>
> Other chapters in "Expert" still use '#' throughout and in
preference of
> '//'.
>
> -W
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev