From: Firstname Surname Date: 2006-08-18T16:58:31+09:00 Subject: Re: Syntax checker wtf? Gregor Kopp wrote: > As "Firstname Surname" said, the error messages from the ruby > interpreter are not really significant, they could be more verbose. > Maybe Ruby 2.0 will do it better. > However, a good editor may help, but it can not be the solution, or? > > Regards, Gregor > > > > Robert Klemme schrieb: I think the syntax checker could be a little more verbose, and I don't think it would take much work. The trouble I had was with a line that had an extra '.' like: @entry = Entry.find(params[:id]. instead of @entry = Entry.find(params[:id] and another error that i think was just a missing bracket maybe like @entry = Entry.find(params[:id I've used many different languages with various levels of syntax error help, but never one this bad. I just wrote a quick script to remove functions from 'def' to 'end' in order and check the syntax over, thus quickly finding which function the error is in. This is a lot better than looking through a couple hundred line controller file. If I can do this in 10 minutes, I can't help but think it's just laziness on the part of the syntax checker not to provide at least hints where it thinks the problem might be. I understand that ruby is flexible (I'm not not sure this is a merit when using for a large web app), but the checker could easily check based on 'standard' expected syntax and be more helpful about error location 99% of the time. -- Posted via http://www.ruby-forum.com/.