Hi Thomas, > [...] I considered it too > tedious to feed file information to the comments parser, especially when > it is usually so easy to locate offending entries by just grepping for the > strings from the console warnings. > [...] Really? With THAT argument you can avoid implementing some things? Nice job you have ;) Really I am more concerned about 'issues' that might not be that easy to find or interpret...
> [...] > Mh, which other improvements are you hinting at? - But anyway, all > important improvements are listed in the release notes [2]. To let the > migration job also warn about JSDoc comments might be doing too much. It > is probably much more important to let the users know about changes > affecting their *code* before worrying about comments, and even when > focusing on the former I'm not sure everybody is reading the information. > [...] I don't want everything to be done by the migration job. -That would really be too much. I just couldn't find for example any hint/notice on the web about the introduction of the '--verbose' command-line switch anywhere. So I keep my strategy for updates/migrations: "generate a dummy application project and compare the generated scripts" Regards, Peter ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
