Yes, this is just declaration before use. I'm actually a fan of that, however, because it can help to catch typos that are hard to find otherwise. In a case like this, where a "name" needs to be registered once and used many times I think it's the right way to go. This is similar to how tasks must be defined before use (or else the weird 'string' notation must be used...).
On Wed, Aug 26, 2009 at 11:14 AM, Russel Winder < [email protected]> wrote: > On Wed, 2009-08-26 at 10:30 -0400, John Murph wrote: > > How about > > > > dependencies { > > defineSet compile > > compile 'commons-io:commons-io:1.4" > > } > > > > Allows explicit definitions of dependencies without making me put > > those is a separate closure from where I'm gonna use them. The > > drawback is that defineSet is now unusable as a dependency set, but > > that doesn't seem too bad. > > > Isn't this just declaration before use? > > Why do I have to declare my variable names, this is a dynamic language: > if I use the compile dependency object/configuration/thingy/blob can't > that cause the creation of the oogimiflip that is needed in the > underlying infrastructure. > > Hummm... re-reading that either I am trying to far too satirical for my > own good, or the pain-killers are wearing off. > > -- > Russel. > > ============================================================================= > Dr Russel Winder Partner > xmpp: [email protected] > Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 > 41 Buckmaster Road, f: +44 8700 516 084 voip: > sip:[email protected] <sip%[email protected]> > London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder > -- John Murph Automated Logic Research Team
