feature literals for task dependencies

6 views
Skip to first unread message

Stephen Haberman

unread,
Dec 24, 2010, 6:12:19 PM12/24/10
to aardv...@googlegroups.com
Hi,

I wonder if you could specify task dependencies with feature literals, e.g.:

@Depends(#compile)
function jar() {
}

I suppose the trick would be that if two tasks both depend on compile, I would not be surprised if each #compile literals ends up with a new object instance, so it'd be hard to tell that they both pointed back to the same underlying function.

Might be more straightforward to just use object instances, e.g.:

compile = task(\ ->
   ...
)

jar = task(\ ->
  ...
).depends_on(compile)

Eh, the task/block syntax is a little funky. Sorry, I'm not an expert on build tools, I was just checking out aardvark and got side tracked. Feel free to ignore me, aardvark as is already looks much nicer than ant. :-)

Love the name, btw.

- Stephen

Brian Chang

unread,
Dec 24, 2010, 6:51:05 PM12/24/10
to aardv...@googlegroups.com
Hi Stephen -

I like your style! We absolutely are planning on getting feature literals in for target dependencies.  If feature literals are available now in Gosu 0.8 (I haven't taken a look in recent weeks), this will be one of my top priorities after I update our Gosu libraries.  Carson Gross should key in - Carson?

Don't worry, we won't have to worry about multiple object instances of feature literals - they're still merely target name references that we feed into Ant, which then takes care of target execution.

Brian

Reply all
Reply to author
Forward
0 new messages