the OO metaphor
Fri Dec 1 12:50:49 CET 2000
Ulf Wiger wrote:
> Perhaps, in response to Bjarnes post, it could be called $reuse_api()
> or something, to avoid getting our feet stuck in the OO mud.
> With a function like $reuse_api(),
> - code reuse is still explicit, but perhaps less so
> - you can opt to have functions dynamically added to your API,
> by specifying that "all functions in API M are also part of
> this API.
> - Incompatible changes in a reused API will break other APIs, but
> this is hard to solve without resorting to (1): copy and paste.
These sort of things would become much cleaner if we had Richard O'Keefe's
idea of 'internal exports' (so for example the functions currently exported
for gen_server callbacks wouldn't become part of the API).
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions