Re: policy suggestion: API docs are not for users
- To: "T. Alexander Popiel" <popiel@wolfskeep.com>
- Cc: Mark Howard <mh@tildemh.com>, debian-java <debian-java@lists.debian.org>
- Subject: Re: policy suggestion: API docs are not for users
- From: Joe Phillips <joe.phillips@innovationsw.com>
- Date: 02 Jan 2003 16:36:54 -0500
- Message-id: <1041543414.2107.105.camel@archaeopteryx>
- In-reply-to: <20021231225311.31F2B2DEDF@cashew.wolfskeep.com>
- References: <1041363880.2837.203.camel@pathfinderii.chu.cam.ac.uk> <20021231225311.31F2B2DEDF@cashew.wolfskeep.com>
On Tue, 2002-12-31 at 17:53, T. Alexander Popiel wrote:
> Thus, the API is in the end-user docs, not just the developer docs.
> I suppose that one could argue that anyone trying to use ant for
> their own programs (instead of just using it as an incidental tool
> for building someone else's program) should install an ant-dev package,
> too... but that seems slightly strange to me, since the person is
> still acting as an end-user for the tool, instead of incorporating
> it into their program.
While you are correct in saying that in some cases, in order to use ant
you need to extend it, I do feel that by extending ant, you then become
an ant developer.
IMHO, it would be appropriate to have a separate package for those
intending to extend ant as opposed to use it as-is.
-joe
--
Innovation Software Group, LLC - http://www.innovationsw.com/
Business Automation Specialists
UNIX, Linux and Java Training
Reply to: