Mailing-List: contact general-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@poi.apache.org
Received-SPF: pass (nike.apache.org: domain of nick.burch@alfresco.com
 designates 207.126.144.127 as permitted sender)
Date: Thu, 25 Aug 2011 10:16:07 +0100 (BST)
From: Nick Burch <nick.burch@alfresco.com>
To: general@poi.apache.org
Subject: Re: HWPF implications of being in the scratchpad
In-Reply-To: 
 <CAPwFv4aXhM0vUt8edsfJLOJX7LmHrMf3LkZD+sMwPDpcApxuyg@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1108251013290.15722@urchin.earth.li>
References: 
 <CAPwFv4aXhM0vUt8edsfJLOJX7LmHrMf3LkZD+sMwPDpcApxuyg@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 25 Aug 2011, Valentin Jacquemin wrote:
> What are the implications of saying HWPF is in the scratchpad, does it 
> mean that the project is not stable enough to be used?

The main thing is that the API isn't fixed. We try to keep compatibility 
on the things in the main jar between releases, often binary compatibility 
but we should always have source compatibility. For scratchpad, the API 
isn't as mature so we don't make the same promises. Generally hand-in-hand 
with that is that the code in scratchpad isn't as full-featured, and 
possibly doesn't handle as many cases.

> After browsing the dev-list it seems it's still in active development 
> and maybe [1] is not up to date, thus my question.

I think we need to tempt Sergey to update the hwpf page with some of his 
recent changes :)

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@poi.apache.org
For additional commands, e-mail: general-help@poi.apache.org