Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #32951 > unrolled thread
| Started by | Manuel Collado <m.collado@domain.invalid> |
|---|---|
| First post | 2015-10-28 10:17 +0100 |
| Last post | 2015-12-02 16:30 -0800 |
| Articles | 4 — 3 participants |
Back to article view | Back to comp.lang.java.programmer
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Teaching "purely object-oriented" Java Manuel Collado <m.collado@domain.invalid> - 2015-10-28 10:17 +0100
Re: Teaching "purely object-oriented" Java Lew <lewbloch@gmail.com> - 2015-11-29 23:05 -0800
Re: Teaching "purely object-oriented" Java Arne Vajhøj <arne@vajhoej.dk> - 2015-11-30 20:13 -0500
Re: Teaching "purely object-oriented" Java Lew <lewbloch@gmail.com> - 2015-12-02 16:30 -0800
| From | Manuel Collado <m.collado@domain.invalid> |
|---|---|
| Date | 2015-10-28 10:17 +0100 |
| Subject | Re: Teaching "purely object-oriented" Java |
| Message-ID | <n0q3tc$2ln$1@speranza.aioe.org> |
El 27/10/2015 23:17, Stefan Ram escribió:
> Some people complained that Java was not »purely
> object-oriented« because one is forced to use non-static
> methods.
This is a questionable argument. Classes are in fact higher-order
objects. So, why shouldn't them have no methods?
Class methods are as pure OO feature as higher-order functions in pure
functional programming.
> For example, in teaching Java, one has to write:
>
> public final class Main
> { public static void main( final java.lang.String[] args )
> { java.lang.System.out.println( "Hello world!" ); }}
>
> with a /static/ method.
Well, you can avoid it. But consider that the unavoidable 'new' operator
is in fact a static method of the Object class.
Just an opinion.
--
Manuel Collado - http://lml.ls.fi.upm.es/~mcollado
[toc] | [next] | [standalone]
| From | Lew <lewbloch@gmail.com> |
|---|---|
| Date | 2015-11-29 23:05 -0800 |
| Message-ID | <5261e594-af18-463c-8971-9781f23cbdd5@googlegroups.com> |
| In reply to | #32951 |
Manuel Collado wrote: > Well, you can avoid it. But consider that the unavoidable 'new' operator > is in fact a static method of the Object class. > > Just an opinion. The 'new' operator is not a method, static or otherwise, of any class. Just a fact. -- Lew
[toc] | [prev] | [next] | [standalone]
| From | Arne Vajhøj <arne@vajhoej.dk> |
|---|---|
| Date | 2015-11-30 20:13 -0500 |
| Message-ID | <n3is7q$mdj$1@speranza.aioe.org> |
| In reply to | #33242 |
On 11/30/2015 6:52 AM, Stefan Ram wrote: > Lew <lewbloch@gmail.com> writes: >> Manuel Collado wrote: >>> Well, you can avoid it. But consider that the unavoidable 'new' operator >>> is in fact a static method of the Object class. >>> Just an opinion. >> The 'new' operator is not a method, static or otherwise, of any class. > > C++ has an »operator new«. In Java, »new« is not an operator. And this happens to be a Java group ... Arne
[toc] | [prev] | [next] | [standalone]
| From | Lew <lewbloch@gmail.com> |
|---|---|
| Date | 2015-12-02 16:30 -0800 |
| Message-ID | <1ed1c4ad-db11-48a1-9250-79ea68c7474e@googlegroups.com> |
| In reply to | #33252 |
Arne Vajhøj wrote: > Stefan Ram wrote: > > Lew writes: > >> Manuel Collado wrote: > >>> Well, you can avoid it. But consider that the unavoidable 'new' operator > >>> is in fact a static method of the Object class. > >>> Just an opinion. > >> The 'new' operator is not a method, static or otherwise, of any class. > > > > C++ has an »operator new«. In Java, »new« is not an operator. > > And this happens to be a Java group ... I stand corrected. The 'new' *keyword* is not a method, static or otherwise, of any class. Now it's just a fact. -- Lew
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.java.programmer
csiph-web