export_to (Was: Re: the OO metaphor)

Sean Hinde <>
Fri Dec 1 14:02:20 CET 2000

> Could someone explain to me how in practice you actually get in
> trouble from not having export_to?

I was thinking from several points of view:

1) Code understanding - It is not just the gen_server callbacks which one
sees with these properties. In gen_fsm for example there are all the
functions which are named after the states - in a big one it can be hard to
see the wood from the trees. Also in some of the big OTP apps there are
often little sub processes kicked off for various reasons which also result
in more "internal" exports.

2) To make systems for code browsing look prettyier / mean more. I guess
this includes automated tools for presenting an overall view of a large
complicated system without cluttering the picture with extraneous stuff. 

3) Ulf's reason!

- Sean

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 mailing list