[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PATCH: NSPathUtilities etc
From: |
Richard Frith-Macdonald |
Subject: |
Re: PATCH: NSPathUtilities etc |
Date: |
Wed, 17 Mar 2004 06:11:40 -0500 |
On 11 Mar 2004, at 01:06, Sheldon Gill wrote:
I don't like having to use configure everything I want to change some
behaviour option or default location for something _within_ the
library.
For example, my patch makes PLATFORM_SUPPORT an optional thing. Should
you
have to re-run configure to turn it on/off?
Why not? Re-running configure is usually quite quick/easy as it
generally
has cached information about the last run.
Having all the options in configure keeps them in one place and is
therefore
easier to maintain than having stuff scattered in various files (and
easier for
users to find things).
Actually, as a general thing, I'd like to decrease the number of
configurable
options and automate everything as much as possible ... ease of use for
newcomers is an important consideration which tends to get overlooked
by experienced developers (myself included).
- Re: PATCH: NSPathUtilities etc, (continued)
- Re: PATCH: NSPathUtilities etc, Alexander Malmberg, 2004/03/08
- Re: PATCH: NSPathUtilities etc, stefan, 2004/03/10
- Re: PATCH: NSPathUtilities etc, Sheldon Gill, 2004/03/10
- Re: PATCH: NSPathUtilities etc, Sheldon Gill, 2004/03/10
- Re: PATCH: NSPathUtilities etc, Alexander Malmberg, 2004/03/13
- Re: PATCH: NSPathUtilities etc, Richard Frith-Macdonald, 2004/03/15
- Re: PATCH: NSPathUtilities etc, Sheldon Gill, 2004/03/16
Re: PATCH: NSPathUtilities etc, Sheldon Gill, 2004/03/13
- Re: PATCH: NSPathUtilities etc,
Richard Frith-Macdonald <=