(Accidentally sent to Colin as private mail, reposting verbatim here;
sorry for the disturbance...)
Well, this naming issue is all about overloading... To circumvent the
overloading problem, we can also use some other name pairs like
`start'/`stop' or `begin'/`end' (Gentoo and LaTeX user here ;). But
that introduces another problem: more names to remember.
So this is somewhat a dilemma. Different context and developers might
lead to different decisions; I personally would rather like to support
overloading the `run'/`finish' name pair, for the similar reason for
Unix's choice of the `x' permission bit to represent both "executable"
for files and "enter-able" for directories: they are loosely correlated
concepts in orthogonal "subspaces".
The same reason explains why I think `up'/`down' are worse names:
because `run'/`finish' (in longruns) and `up'/`down' (in longruns) seem
much less correlated than `up'/`down' (in longruns) and `up'/`down' (in
oneshots currently).
On Sat, Sep 19, 2015 at 08:50:53PM -0700, Colin Booth wrote:
> I don't know about anyone else, but I actually like the difference. ./up
> and ./down are the things that fire when it goes up and down. Using run and
> finish is more confusing since it overloads the functionality semantics of
> longruns (technically so does up and down, but since s6-rc precludes the
> use of manual down files it's less of an issue).
--
My current OpenPGP key:
4096R/0xE18262B5D9BF213A (expires: 2017.1.1)
D69C 1828 2BF2 755D C383 D7B2 E182 62B5 D9BF 213A
Received on Sun Sep 20 2015 - 07:15:52 UTC