Bugzilla – Full Text Bug Listing
| Summary: | Parse fails when IfStatement is return | ||
|---|---|---|---|
| Product: | [Technology] DLTK | Reporter: | Mark Howe <mark.howe> |
| Component: | Ruby | Assignee: | dltk.ruby-inbox <dltk.ruby-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 0.9 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
It seems to be already fixed. Thanks, anyway. bulk change: this bug was fixed in DLTK 0.9 |
The following fails with a ClassCastException in RubyASTBuildVisitor.visitReturnNode. An attempt is made to cast the IfStatement to an expression and add it to the RubyReturnStatement's CallArgumentsList. It looks like you are aware of the problem, as there is a comment in ExpressList to change it to a StatementList or a add a statement to expression converter. I was trying to find a way to make this specific case work but seems like a more global issue. A place in the rails codebase this affects is activerecord/associations/has_one_association.rb. def m(b) unless b return false end end