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

Re: building "path expressions"

From	markspace <markspace@nospam.nospam>
Newsgroups	comp.lang.java.programmer
Subject	Re: building "path expressions"
Date	2014-01-23 15:33 -0800
Organization	A noiseless patient Spider
Message-ID	<lbs8sl$blq$1@dont-email.me> (permalink)
References	(1 earlier) <lbru26$8dv$1@dont-email.me> <nesting-20140123220949@ram.dialup.fu-berlin.de> <lbs32v$607$1@dont-email.me> <path-expressions-20140123230350@ram.dialup.fu-berlin.de> <lbs587$im7$1@dont-email.me>

Show all headers | View raw

On 1/23/2014 2:29 PM, Jeff Higgins wrote:
>
> Why would one want type information visible in your "path expression".
>

Removing the operator overloading would convey type information.

- binds package to class.
^ binds class to subclass
: binds class to field

package a.b.c;
class G { int h = 8; }
class F { G g = new G(); }
class d { static class e { static F f = new F(); }}

becomes

   a.b.c-d:e^f:g:h

But no one thinks that way, or wants to.  The type information is there, 
but the example really isn't better for it.  Better to use names that 
convey information than to make funny symbols that look like your cat 
walked on the keyboard.

R.layout.main is an unfortunate example of not using names to properly 
convey information.  It's a quirk of working with actual human beings 
that we all have to put up with this sort of thing on occasion.

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

Thread

Re: building "path expressions" Jeff Higgins <jeff@invalid.invalid> - 2014-01-23 15:27 -0500
  Re: building "path expressions" Jeff Higgins <jeff@invalid.invalid> - 2014-01-23 16:11 -0500
  Re: building "path expressions" Jeff Higgins <jeff@invalid.invalid> - 2014-01-23 16:52 -0500
    Re: building "path expressions" Jeff Higgins <jeff@invalid.invalid> - 2014-01-23 17:29 -0500
      Re: building "path expressions" markspace <markspace@nospam.nospam> - 2014-01-23 15:33 -0800

csiph-web