Re: Tip: automating EOGenerator
Re: Tip: automating EOGenerator
- Subject: Re: Tip: automating EOGenerator
- From: Lachlan Deck <email@hidden>
- Date: Fri, 12 Jan 2007 17:25:14 +1100
Hi Chuck,
On 12/01/2007, at 4:31 PM, Chuck Hill wrote:
On Jan 11, 2007, at 9:18 PM, Lachlan Deck wrote:
print "'Declaring' the problem: ant's lack of a basic loop
structure makes simple things more complex than need be. Having to
create a custom framework to provide the spoon?.\n";
Is that better? :-)
er, no.
http://en.wikipedia.org/wiki/Declarative_programming
You are just too used to procedural or imperative thinking. Think
Different.
No, I'm just pointing out that the user-contributed task 'foreach'
should have been included in the default install of ant. That's an
oversight imo. Without such a task - what I wanted to achieve could
_not_ be declared with the default ant library.
Here's what could be done if it was there...
<path id="path">
<fileset dir="${basedir}/Resources">
<include name="*.eogen"/>
</fileset>
</path>
<pathconvert pathsep="," property="list" refid="temp"/>
<foreach list="${list}" target="eogenerate" param="file"/>
without it?
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden