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.
Product Version = NetBeans IDE Dev (Build 200910080418) (#4925e52d6715) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02; Sun Microsystems Inc. Steps to reproduce. - Copy the code to the editor -------------------------------------------------------------------- class A{ var i = 3; var num = 3.0; var b = true; var c = "2".charAt(0); var byte:Byte = 1; var short:Short = 2; var long:Long = 3; var float:Float = 5.0; var double:Double = 10.0; var date = 3h; var str = "Hello!"; var a:A; var f = function(a:Number, b:String):Boolean { true }; var seqf = function(a:A[], b:String[]):Boolean[] { [] }; var seq = ["1", "2", "3" ]; } var a = A{}; println(a); -------------------------------------------------------------------- - Set a breakpoint to the last line - Debug the file - Go to the Local Variables window - Expand the 'a' variable It contains 'javafxapplication$Main$A$i' attribute instead of 'i' It contains 'javafxapplication$Main$A$num' attribute instead of 'num' And etc.
Byte, Short, Long, Float and Double types are not JavaFX types. - proper types for i and num are fixed
changeset, TM ?
Changeset!
Try this one : 2660:9faf379a65c7
> Byte, Short, Long, Float and Double types are not JavaFX types. They are the JavaFX types. See http://openjfx.java.sun.com/hudson/job/openjfx-compiler/lastSuccessfulBuild/artifact/dist/doc/reference/TypeChart.html So the debugger should show the Byte type instead of the byte and so on. Also check what the Navigator shows for these types. For example it shows 'f:function(:Float,:java.lang.String):Boolean' instead of com.sun.javafx.functions.Function2. The debugger should show the same type.
Created attachment 90126 [details] Data types in the Navigator
This is issue similar to the 172193 so I'm closing it as duplicate. *** This issue has been marked as a duplicate of 172193 ***
I am sorry. The issue 172193 is the profiler issue "AssertionError: nps param should not be empty". It is not related to the current issue.
Sorry, the issue should be 172460 *** This bug has been marked as a duplicate of bug 172460 ***
verified as duplicate.