Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #15230

Re: Single Class Object Model - new release

From Robert Klemme <shortcutter@googlemail.com>
Newsgroups comp.lang.java.programmer
Subject Re: Single Class Object Model - new release
Date 2012-06-12 23:33 +0200
Message-ID <a3pqt1FsnpU1@mid.individual.net> (permalink)
References (2 earlier) <787f166d-488f-49fe-aa1f-bd8e227ed30e@eh4g2000vbb.googlegroups.com> <lcadnWBpeIcAPEvSnZ2dnUVZ8gydnZ2d@giganews.com> <169b14d7-e43d-482d-a195-bcd20965331a@d17g2000vbv.googlegroups.com> <b65de1ac-27ff-4b67-ab57-ed0e83a18766@googlegroups.com> <0527b567-b7b6-4f79-b675-08993ba77b88@x21g2000vbc.googlegroups.com>

Show all headers | View raw


On 12.06.2012 22:03, micha wrote:

> Yes it's inconsistent:
> - because [] and ArrayList/Collections are 2 different ways to handle
> vectors/lists (while there is only 1 in Python/Lisp/Perl

The term is not "inconsistency" but "variety": different situations 
require different list like structures for efficient handling.  You make 
it sound like having only one data structure for an abstract concept 
would be a value in itself.  That might be true in mathematics but not 
in a software developer's real life(TM) because even though some 
requirements are identical (ordered storage) many others might not (e.g. 
varying size vs. fixed size).

> - because int is a primitive type (like in procedural languages)
> while Integer are Objects (the bypass to put integers in a Collection
> in fact)

Oh, Integer can serve other purposes as well: by having an object 
reference you can encode more information, namely "value absent" and 
"specific int value X".  The argument that Java is somehow deficient 
because it mixes primitive types with object types is not new.  The fact 
has some drawbacks (some of which were fixed with autoboxing) but it 
also has advantages.

>    instead all entities in Scala/Smalltalk are Objects (even
> functions), and scripting language (Python/Perl/PHP/Lisp) provide lazy
> typing and are thus
>    more consistent (even if at the price of more risk to write
> erroneous code which language laziness will let go through)

I don't see an increased risk here.  Strong typing prevents misuse.  And 
the term used for Ruby & Co. is "dynamic typing" not "lazy typing", 
while also these languages have strong typing (i.e. every object has a 
specific type all the time).  It's just that variables and expressions 
do not have a type which can be statically determined.

I would not call these languages more consistent.  It's just a different 
concept and mindset - dynamic vs. static typing.

Kind regards

	robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

Back to comp.lang.java.programmer | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Single Class Object Model - new release micha <kernmichel@yahoo.fr> - 2012-06-11 15:45 -0700
  Re: Single Class Object Model - new release Lew <lewbloch@gmail.com> - 2012-06-11 16:38 -0700
    Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-11 18:39 -0700
      Re: Single Class Object Model - new release Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-06-11 20:55 -0500
        Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-11 21:42 -0700
          Re: Single Class Object Model - new release Robert Klemme <shortcutter@googlemail.com> - 2012-06-12 18:24 +0200
            Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-12 13:09 -0700
              Re: Single Class Object Model - new release Robert Klemme <shortcutter@googlemail.com> - 2012-06-12 23:48 +0200
                Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-13 01:12 -0700
                Re: Single Class Object Model - new release Robert Klemme <shortcutter@googlemail.com> - 2012-06-13 06:44 -0700
                Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-13 15:22 -0700
                Re: Single Class Object Model - new release Robert Klemme <shortcutter@googlemail.com> - 2012-06-14 00:56 -0700
                Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-14 03:24 -0700
                Re: Single Class Object Model - new release Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-06-14 12:27 -0500
          Re: Single Class Object Model - new release Lew <lewbloch@gmail.com> - 2012-06-12 10:05 -0700
            Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-12 13:03 -0700
              Re: Single Class Object Model - new release Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-06-12 15:58 -0500
                Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-13 02:08 -0700
              Re: Single Class Object Model - new release Robert Klemme <shortcutter@googlemail.com> - 2012-06-12 23:33 +0200
              Re: Single Class Object Model - new release markspace <-@.> - 2012-06-12 15:15 -0700
                Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-13 02:57 -0700
                Re: Single Class Object Model - new release markspace <-@.> - 2012-06-13 08:26 -0700
                Re: Single Class Object Model - new release micha <ludicite@gmail.com> - 2012-06-13 15:17 -0700
                Re: Single Class Object Model - new release Lew <noone@lewscanon.com> - 2012-06-13 19:06 -0700
                Re: Single Class Object Model - new release markspace <-@.> - 2012-06-13 19:15 -0700

csiph-web