cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yang Yang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-2937) certain generic type causes compile error in eclipse
Date Thu, 21 Jul 2011 23:23:57 GMT
certain generic type causes compile error in eclipse
----------------------------------------------------

                 Key: CASSANDRA-2937
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2937
             Project: Cassandra
          Issue Type: Bug
            Reporter: Yang Yang
            Priority: Trivial


the code ColumnFamily and AbstractColumnContainer uses code similar to the following (substitute
Blah with AbstractColumnContainer.DeletionInfo):



import java.util.concurrent.atomic.AtomicReference;
public class TestPrivateAtomicRef {
    protected final AtomicReference<Blah> b = new AtomicReference<Blah>(new Blah());
    // the following form would work for eclipse
//    protected final AtomicReference b = new AtomicReference(new Blah());

    private static class Blah {
    }
}


class Child extends TestPrivateAtomicRef {    
    public void aaa() {
        Child c = new Child();
        c.b.set(
        b.get()  //<==== eclipse shows error here
        );
    }
}


in eclipse, the above code generates compile error, but works fine under java command line.
since many people use eclipse, it's better to 
make a temporary compromise and make DeletionInfo protected

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message