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

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

Re: building "path expressions"

Show all headers | View raw

On 01/23/2014 12:37 PM, Stefan Ram wrote:
>    When creating an interface for a library, sometimes one wants the user
>    to see nesting in a »path expression«, like for example »a.b.c.d.e.f.g.h«
>    to convey the idea that h is a part of g, which is a part of f, and so on.
>
>    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
>    implement a »path expression« »a.b.c.d.e.f.g.h« might be:
>
> 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(); }}
> public final class Main
> { public static void main( String[] args )
>    { java.lang.System.out.println( a.b.c.d.e.f.g.h );  }}
>
If you nest that deep, stand by for a lot of NPEs. :-)

AHS
-- 
When a true genius appears, you can know him by this sign:
that all the dunces are in a confederacy against him.
-- Jonathan Swift

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

Thread

Re: building "path expressions" Arved Sandstrom <asandstrom2@eastlink.ca> - 2014-01-23 17:52 -0400
  Re: building "path expressions" Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-01-23 23:24 -0800

csiph-web