On Thu, 13 Sep 2001 03:03, Peter Janes wrote: > Peter Donald wrote: > > So instead of > > > > <project name="foo" default="..." > > > > > you would have > > > > <project default="..." > > > <property name="name" value="foo" /> > > > > And that works fine ;) Instead of name you could even use > > ant.project.name as name of property and have it fully compatible ;) > > So why bother naming projects,
I don't and nor do any I get my hands on ;) > then, if the name can't actually be used > anywhere? Or is that your point? I am not sure I follow you. The name attribute of project is just a special-case property. My opinion is that it should be handled like every other property. > Isn't staying out of the ant.* namespace, especially in user files, a Good > Thing? Sure, it's not explicitly forbidden, but since we're talking about > evil programming, maybe it should be.... Probably but then again I don't think there needs to be much in a ant.* namespace ;) The one property that I think *should* be in namespace are ant.version (useful for future compatability). The others (ant.home, ant.project.name, ant.file etc) are essentially work-arounds because ant currently doesn't have a great interface between tasks and the runtime (however hopefully this will change in Ant2). -- Cheers, Pete ---------------------------------------------------------------- Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it. -- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982 ----------------------------------------------------------------
