[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-hackers] Exposing internal APIS

From: Felix Winkelmann
Subject: [Chicken-hackers] Exposing internal APIS
Date: Fri, 12 Sep 2014 12:31:00 +0200 (CEST)

Hello, again!

If I understand this correctly, then you want to expose the internal
threading stuff in scheduler.scm as a module?

I think this should be avoided - we tie our hands behind our backs by
doing this. Once we fix the interface to deeply internal functionality
like the scheduler and the low-level threading operations, any changes
need to be made in a backwards-compatible manner, creating
workarounds, bloat and complexity.

There is practically no advantage for the user (who just wants a
simple, stable interface with error checking), and many disadvantages
for use. It is true that certain eggs will use internal functionality
(srfi-18), but these are written and maintained by us, so we can do
the necessary steps to keep core and eggs in sync, hopefully knowing
well enough what has to be done in case the internals change.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]