[rules-dev] Compiler API - changes?

[Michael Neale]

* Firstly, a simpler higher level API, like the RuleBaseLoader - for dealing
with simple cases (a High Level API that compiles and builds in one step).
* Secondly - I don't see why we have to expose the descrs in the normal case
- we can just have an api that goes from source to Package binary  - make it
optional to extract the Descrs.

* Perhaps something like:

PackageBuilder.addPackageHeader(... stuff for package header... only done
once... eg globals, imports... validate it all at this point).
PackageBuilder.addRule(... just takes the reader to a single rule...)
PackageBuilder.addDrl(... just takes a reader to a chunk of DRL, but does
NOT include the package header? Or if it does, it works jsut as before,
merging the package).
PackageBuilder.addFunction...

you get the idea. Its really augmenting it for the repo/individual rule
assets/files.




On 2/28/07, Mark Proctor <mproctor at codehaus.org> wrote:
>
>  Suggest away.
>
> Mark
> Michael Neale wrote:
>
> Guys - are there going to be any changes to the compiler API now? Cause
> now is the time to fix/change it if needed.
>
> I have some suggestions if anyone is interested.
>
> ------------------------------
>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-dev
>
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20070228/4ddc3563/attachment.html