[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] [PATCH] Move `system' into (chicken base)
From: |
Peter Bex |
Subject: |
Re: [Chicken-hackers] [PATCH] Move `system' into (chicken base) |
Date: |
Mon, 25 Dec 2017 13:43:20 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Mon, Dec 25, 2017 at 03:13:38PM +1300, Evan Hanson wrote:
> Hi hackers,
>
> Here's a small patch that does just what it says.
I thought about this for a bit, but I disagree with moving just this into
chicken.base. This would be arbitrary and confusing, given that "qs"
(which belongs together with system) is in chicken.process, and also other
things like process-execute which perform basically the same thing that
system does.
> The reason I'd like to put `system' in the "base" library instead of
> "process" (as c-l-r has it) is twofold; one, it's generally useful and
> nice to have on hand without having to import extra libraries
That goes for many other things too. For example, the fixnum procedures
are used a *lot* in core, yet they are in chicken.fixnum.
> and two, it's mostly implemented in runtime.c so there's not actually any
> benefit
> to putting it in the process module (from a program size point of view,
> I mean). Let me know what you think.
For me it's more about what makes the most sense to an end user. The
more logical the module layout is, the better. Like I explained above,
I think this patch works against that, because one would _expect_ system
to be in chicken.process.
Cheers,
Peter
signature.asc
Description: PGP signature