I find using strings as identifiers somewhat infelicitous -- I like having language level symbols so as to avoid spelling error issues. Also for me, strings are data not control.
So as a specific single example, I don't like having to use strings for
task names, as in:
defaultTasks ( 'flob' , 'adob' )
However, whilst task names were string everywhere I just got into the
habit of:
def flob = 'flob'
def adob = 'adob'
. . .
defaultTasks ( flob , adob )
But now that task names are not strings in some places whereas they are
in others, things are getting to a "point of pain".
task printHelloWorld << {
println ( 'Hello World.' )
}
defaultTasks ( 'printHelloWorld' )
Is annoying me because the name of the task is not the same sort of
language structure everywhere. Am I on my own here? Have I missed
something? Is there something to think about?
--
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]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
