Yep, that's kind of what I thought would be the case. The only way to do it in Xdoclet I guess would be to introduce some sub-classes, but that's certainly not desirable. I wasn't really suggesting a replacement for iContract, more interested on how you'd go about doing it within Xdoclet.
Thanks for the info. Cheers, David On Wednesday 17 October 2001 10:23, Aslak Helles�y wrote: > It's not a good idea, I promise you. iContract does the job very very > well already. -And it implements a subset of OQL, with quantifiers like > forall, exists and implies. XDoclet (or any other doclet) doesn't give > you access to the source code of the classes being scanned, so you'd > have to implement some pretty fancy parsing (JavaCC or ANTLR) to mix the > code from the javadoc into the class' code. You'd even have to parse > (JavaCC or ANTLR again) the assertion expressions (at least if you want > to do anything fancy like iContract). It would be a huge job, and I > don't see the point in reinventing the wheel anew. > > -And nothing stops you from using iContract with XDoclet. > > See > http://www.reliable-systems.com/tools/iContract/iContract.htm > http://www.javaworld.com/javaworld/jw-02-2001/jw-0216-cooltools.html > > for more info about iContract. > > Cheers, > <aslak/> _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
