From: Geoff E. <gel...@pr...> - 2002-02-28 12:45:57
|
Hi Sven, On Thu, 28 Feb 2002, Sven Ehrke wrote: > Eldridge Geoff <Geo...@tg...> schrieb am 28.02.02: [..] > > I would like to use geant for the task of creating and maintaining > > the short class forms for the elj project. The details of my setup >=20 > I guess you want to use SmallEiffel's "short" commandline tool to do > this. I am just saying this because one day we might be able to produce > the short forms with the help of GOBO and not with tools like > SmallEiffel's 'short'. Nice to know .. Thanks for the following details .. it has helped me a lot to understand what is happening. I am not desparate for the behaviour to be implemented, please implement in your own time, I can wait. Thanks .. GEoff > Now to your question: > The answer at the moment is no. I'll try to show a possible way > how to improve geant to support this: >=20 > Currently the fileset/map combination > is able to select the files you want: > ___________________________________________________________ > <fileset > directory=3D"${ELJ}" > include=3D"@(lib/ccl/**/*.e|lib/common/eiffel/common)" > /> > ___________________________________________________________ >=20 > But to use SmallEiffel's 'short' tool you have to use the <exec> > task: >=20 > <exec executable=3D"short ..."/> >=20 > Now the <exec> task does not support a nested <fileset> element but > I think it would make sense if it would. > It could look like this for example: > __________________________________________________________ > <exec executable=3D"short -html2 ${fs.filename} > ${fs.mapped_filename}"> > <fileset > directory=3D"${ELJ}" > include=3D"@(lib/ccl/**/*.e|lib/common/eiffel/common)" > > > <map type=3D"glob" from=3D"*.e" to=3D"*.html"/> > </fileset> > </exec> > ___________________________________________________________ >=20 > ${fs.filename} and ${fs.mapped_filename} here would be > variables set while iterating over the fileset > right before the 'executable' argument is evaluated and executed. > It should also be possible to define these names like it is done with > the <outofdate> task. >=20 > The fileset task probably has to provide another boolean attribute > called for example 'include_outofdate' (which is only available with > a nested <map> element): > ___________________________________________________________ > <fileset > directory=3D"${ELJ}" > include=3D"@(lib/ccl/**/*.e|lib/common/eiffel/common)" > include_outofdate=3D"false" > > > <map type=3D"glob" from=3D"*.e" to=3D"*.html"/> > </fileset> > ___________________________________________________________ > By specifying 'false' for 'include_outofdate' we only include > that eiffel files which are newer than their corresponding html files. >=20 > >=20 > > I must admit I have no idea how the map works. >=20 > Yes. Sorry about the lack of documentation. > We are currently working on how to produce documentation in GOBO. > I am trying to keep >=20 > $GOBO/examples/geant/** >=20 > up to date. Maybe this helps a bit. The wildcard syntax for filesets > works like in bash with the exception that '**' means arbitrary deep > directories. >=20 > If nobody has objections or better ideas I'll start to implement > it. >=20 > Geoff: > I hope you can wait some days until this is supported. >=20 > Thank you very much for your input. >=20 > - Sven >=20 >=20 > _________________________________________________________________________= _____ > 100 MB gute Gr=FCnde! Jetzt anmelden und FreeMail-Speicher erweitern f=FC= r > Sprach-, Fax- und Mailnachrichten unter http://club.web.de/?mc=3D021103 >=20 >=20 > _______________________________________________ > gobo-eiffel-develop mailing list > gob...@li... > https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop >=20 |