For example, in Stephen's suggested structure, it's likely that o.a.c.primitives.list and o.a.c.primitives.map will depend on o.a.c.primitives.collection. Your suggested structure will cause a lot of criss-crossing dependencies between packages, and I think that this will make the code harder to manage and stabilize.
Hope, Matthew wrote:
As a user I would point out that a likely use case would involve one primitive type but lots of different collections of that type.
Would packaging by type work?
I know it has negatives but if most of the code will be done via a template and code generation that it wouldn't be too bad perhaps?
Would mean you import o.a.c.primitives.int.*; and get all the collections / Map and iterators there ready in your ide of choice :�)
Just a thought and I haven't really considered the ramifications in much detail.
Matt
-----Original Message-----
From: __matthewHawthorne [mailto:[EMAIL PROTECTED] Sent: 10 October 2003 22:17
To: Jakarta Commons Developers List
Subject: Re: [primitives] Package layout strategy
Looks good. This will present a nice, easy way to navigate through all of the classes.
Stephen Colebourne wrote:
I've been thinking about how the new project should structure its packages.
[primitives] will (I hope) be looking at Map implementations in addition to the List ones currently existing. I would like to restructure the packages into an interface based scheme. primitives.collection primitives.list
primitives.map
primitives.iterator
Each package would contain the interface, implementation, wrapper and
adaptor.
I believe this will give [primitives] the room it needs to grow, and allow users a quick grasp of the features available. (If you want to see what this turns out like see the sandbox primitives)
However, this is a change from the current layout of the code held in [collections]. So.... I propose that
- the primitive classes in [collections] are imported directly into [primitives] without changing the package name
- we arrange a snapshot build of [primitives] using this package structure
- we reorganize the packages into the new layout
- we head towards a release
How does this sound???
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
**************************************************************************
The information transmitted herewith is sensitive information intended only
for use by the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
