This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
E.g. a = {:a => 'x', :b => 'z'} def foo(param) puts param end v = foo(a) See http://forums.netbeans.org/topic13788.html
Still there.
Hi, Any update for this issue ?
Hi, Could you please fix this issue ? As indicated in my latest post, this is a general issue if the parser is in 1.9 compatibility mode (even if the new hash syntax is not used). This affects the location of all top level elements : - top level variables - top level modules - top level classes - top level functions This is rather annoying. As ruby-1.9.x will be more and more widespread with the upcoming ruby-1.9.2, the fix will benefit a lot of users.
I'll try to give this another look soon, I actually already spent some time investigating this, but didn't figure out the root cause. Hopefully I'll have better luck with a fresh look at this.
I hope that you will be able to find the cause of this issue. Otherwise, there should be at least an option to disable the automatic compatibility mode. When you use JRuby, you have the opportunity to choose the compatibility mode. When you use MRI 1.9.1 (Matz Ruby) the compatibility mode is automatically set to 1.9. A simple temporary workaround could be to offer the ability to disable this behaviour.
Yes, that makes sense. I've wanted to add a combo box for source level in any case as currently switching JRuby to 1.9 mode is a bit awkward.
Hi, Could you please consider fixing this issue or providing a workaround (e.g. choice between 1.9 and 1.8 compatibility mode) ? Thanks.