I need your opinion...

Marek Kozieł develop4lasu at gmail.com
Sat Mar 21 12:52:36 PDT 2009

  There is no point in writing a proposal if people will not use it.
I have found that some parts of programming are problems for me and
for the others,
but you might have a different experience so I would like to hear your
opinion about listed points.

  After some time, I found that there was better solution for consider operator:
Allow final variables and final Fields (except blank final), to not
having explicit Type.

  Consider operator can help in dealing with generics, which are pain
in the as..
I often found that Types took even 50% code, which is insane.

         for ( ComparablePair<String,StatisticsCollector<Days>> pair :
statisticsCollectors ){ … }

Consider operator:
         for ( ::pair : statisticsCollectors ){ … }

New final way:
         for ( final pair : statisticsCollectors ){ … }

New final way & while-each loop:
         while ( final pair : final iterator =
statisticsCollectors.iterator() ){
              if ( ! isValid(pair.getKey()) ) iterator.remove( pair );

Add forget keyword to allow erase variable from current context (block):
   - For method parameters it's now impossible.
   - Assigning null to variable is lame and not possible for final variables.
   - Blocks not always fit to this purpose.

Are glue classes hard to understand?

Blocks in classes:
Peoples often do not use formatters because they do not keep logical
order in class structure, this would allow to define proper grouping.

class Some{
   { // block boo
      private Boo boo;

      public Boo getBoo(){
         return boo;

      public void setBoo(Boo boo){
         this.boo = boo;
   }//end block

Pozdrowionka. / Regards.
Lasu aka Marek Kozieł


More information about the coin-dev mailing list