Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #27387
| From | markspace <markspace@nospam.nospam> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: building "path expressions" |
| Date | 2014-01-23 09:33 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <lbrjq0$89t$1@dont-email.me> (permalink) |
| References | <path-expressions-20140123173039@ram.dialup.fu-berlin.de> |
On 1/23/2014 8:37 AM, Stefan Ram wrote:
> I think it is funny that one can use either package names /or/ nested
> classes /or/ fields to implement such a path, without this choice being
> visible in the »path expression«. For example, one posssibility to
> { java.lang.System.out.println( a.b.c.d.e.f.g.h ); }}
Well I'm not sure what you find "funny" here; possibly that . is used
to both separate a name in package name, and to access a field?
It's not the first example of operator overloading in a language. In
Java, the + operator means integer addition, floating point addition
(two very different things) as well as string concatenation.
But I don't find it funny, merely practical and sensible. Natural
languages use the same word to mean different things as well, why should
mathematical languages be any different?
Back to comp.lang.java.programmer | Previous | Next | Find similar | Unroll thread
Re: building "path expressions" markspace <markspace@nospam.nospam> - 2014-01-23 09:33 -0800
csiph-web