I’d rather they didn’t have a description at all.
# some rather long comment about this involved set of task creation code
xxxxx.each { |y| task ….}With this patch I’d now have to worry about where comments for the *code* have to be located so that it doesn’t interfere with the tasks I’m programmatically creating? Or sprinkle empty desc “” calls everywhere I programmatically create tasks that I don’t want to have task descriptions? Yuck. Perhaps I’m just in a very small minority in that I use rake in a complete build system where almost all tasks are programmatically generated. I guess if I had a bunch of rakefiles with simple file, task, etc. calls in it I wouldn’t be so offended, but given that I have huge bodies of code built around programmatically generating various tasks, this patch really bothers me. I’ve more than said what I needed to say. If no one else cares there’s not much else I can say about it. I already have to patch rake locally with some of my own changes whenever a new version comes out anyway so I guess I can remove this patch as well if it’s ever introduced publicly. Cheers… Patrick From: [email protected] [mailto:[email protected]] On Behalf Of Dave Thomas Sent: Friday, June 05, 2009 11:39 AM To: Rake Development and Discussion Subject: Re: [Rake-devel] Rake DSL Commands are no long in top level Speaking of the patch - how does it handle it when multiple tasks are created on the same line [say in a block iteration]? If there happens to be a comment on the line above they'll all get the same task description? If you don't want that behavior, just use desc, which takes priority... Dave
_______________________________________________ Rake-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/rake-devel
