[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Understanding internal use functions
From: |
Tassilo Horn |
Subject: |
Re: Understanding internal use functions |
Date: |
Tue, 07 May 2019 11:57:24 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
"Paul W. Rankin" <hello@paulwrankin.com> writes:
>> Internal functions/variables usually convey the meaning of "don't
>> rely on me because I might change whenever my author likes". So it's
>> more a hint to programmers than to users.
>
> So I should name a functions as internal as a way to imply "hey don't
> use this in other programs" (for whatever reason)?
Yes. And inversely, if you've written a public (non-internal) function
in your package, better assume that someone somewhere is already using
it in her config, so don't change its interface if not absolutely
necessary.
Bye,
Tassilo