On Monday, 11.01.2016 at 00:37, Antti Kantee wrote:
> >I've pushed some small changes to "rc" on the branch:
> >
> >- use "bg" and "pipe" instead of "&" and "|" for runmode
> >- allow the user to explicitly specify "fg" (thanks to Martin Sustrik for
> >   the tip -- implicit but not specifiable defaults are bad for config
> >   generation tools)
> 
> If you're worried about not being able to specify the default, the right
> change is to fix runmode to be accepted without & or |, and not to start
> renaming terms.  Among other things, renaming closes the door for [...]

Agreed, I hadn't thought of I/O redirection.

I'll change runmode to "&" | "|" | "".

> >Antti's original proposal asked the question of what to do about "argv",
> >specifically about how to specify argv[0]. I had to make a choice there and
> >went for the less-flexible but user-friendly approach of argv[0] == bin,
> >argv[1..N] == args[]. This has the downside of not supporting multi-call
> >binaries.
> >
> >Having thought about it, we could instead specify both argv[] and args[],
> >but make them mutually exclusive. If the user specifies args[] then they
> >get the current behaviour (described above). If the user specifies argv[]
> >then the entire argv[] array gets set from this.
> 
> No, there can be only one [way to specify things].
> 
> Furthermore, since above you were concerned about default parameters, for
> the sake of consistency of your argumentation, what would be the default
> (empty) for args[]?  (one could even wonder what is the explicit
> end-of-argv, if one were really concerned)

My argument was not quite correct -- what I meant was "must be able to
specify equivalent of default". With a default for args[] of [] this would
be fine, since you can specify [] manually.

> Reminder-for-thought: the config format is not the usability layer.  The
> only thing it needs to be is not be an unusability layer (cf. rumprun
> launcher).

Good point, thanks. In that case, should we just go with argv[], and no
default?  I.e. you must specify both binname and at least argv[0]?


Reply via email to