Re: Public vs internal APIs

From: "Markus KARG" <markus(at)headcrashing(dot)eu>
To: "'List'" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Public vs internal APIs
Date: 2015-07-23 16:51:09
Message-ID: 002901d0c567$c6f9fe00$54edfa00$@eu
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Actually I would go with a really flat structure, so we can simply use "default" and "public" visibility of classes to distinguish between API and implementation. If more structure is wanted, we could use "org.postgresql" vs. "org.postgresql.internal" to make it more clear which classes are private and which are published.

Unfortunately Java has no "friends" declaration. :-(

-----Original Message-----
From: Vladimir Sitnikov [mailto:sitnikov(dot)vladimir(at)gmail(dot)com]
Sent: Donnerstag, 23. Juli 2015 18:35
To: Markus KARG
Cc: List
Subject: Re: [JDBC] Public vs internal APIs

> instead restructuring the package hierarchy, as this is was it was invented for originally.

package-private is not enough.
Java9 will have modules for that, however we would have to live with
java8 for a while.

Which package would you suggest for org.postgresql.util.LruCache?

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Vladimir Sitnikov 2015-07-23 17:11:58 Re: Public vs internal APIs
Previous Message Vladimir Sitnikov 2015-07-23 16:35:21 Re: Public vs internal APIs