On Mon, 12 Nov 2001 22:03, Stefan Bodewig wrote: > On Mon, 12 Nov 2001, Peter Donald <[EMAIL PROTECTED]> wrote: > > Or are you saying that <apply /> is a better construct than > > implementing the task properly ? > > Implementing which task properly?
any of them. > <apply> saves you from writing a task in the gcc (or any similar > transformation) case, it is a whole bunch of tasks in one - without a > need for a custom task. yer... > For things like compiling C(++) sources, I'd certainly prefer a custom > task with smart dependency checking and all that, but if my project > contains three or four C files for my JNI stuff and the simple <apply> > task is all I need, then why should I bother writing a task for it? why not? -- Cheers, Pete *------------------------------------------------------* | Despite your efforts to be a romantic hero, you will | | gradually evolve into a postmodern plot device. | *------------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
