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.

Bug 246700 - regression: incorrect erros in template based code
Summary: regression: incorrect erros in template based code
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Compiler (show other bugs)
Version: 8.1
Hardware: All All
: P2 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
: 246727 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-08-26 11:21 UTC by Vladimir Voskresensky
Modified: 2014-08-29 09:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Voskresensky 2014-08-26 11:21:02 UTC 
recent build has the following regression:

  class pair<First, Second> {
    
  }
  
  class MapImpl<KeyT, ValueT> {
    pair<KeyT, ValueT> Buckets[];

    public MapImpl() {
      Buckets = ((pair<KeyT, ValueT>[])null); // Error here
    }    
  }

Error messages are:
lambda expression not expected here

')' expected

')' expected

not a statement

illegal start of expression
Comment 1 Vladimir Voskresensky 2014-08-26 11:21:43 UTC 
Product Version: NetBeans IDE Dev (Build 20140826-6b25e1f88edf)
Java: 1.7.0_67; Java HotSpot(TM) 64-Bit Server VM 24.65-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_67-b01
Comment 2 Vladimir Voskresensky 2014-08-26 11:23:15 UTC 
used source level is Java 1.7
Comment 4 Quality Engineering 2014-08-28 02:39:41 UTC 
Integrated into 'main-silver', will be available in build *201408280001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/24ba456e0bab
User: Dusan Balek <dbalek@netbeans.org>
Log: Issue #246700: regression: incorrect erros in template based code - fixed.
Comment 5 Dusan Balek 2014-08-29 09:38:29 UTC 
*** Bug 246727 has been marked as a duplicate of this bug. ***