> If this is the case and it is undesirable, would you use _any_
> defaults? I have a feeling this is a circular discussion..
I'll declare halt if we appear to be truly circular, which is to
say we would be producing expressions to no apparent effect. This
does not appear to be the case yet. Audience, you have veto power
here.
As I have done so in the real world, it would appear that a
reasonable statement would be "yes, I do and would do so again".
What makes my original statement tangental, at least in my case,
is that once I went to the trouble of specifying syslog.conf, I would
*probably* always go to the trouble of specifying it, even if I hid
the detail such that it was effectively a linguistic constant after I
specified it the once.
I can see gotchas in here, but nothing truly awful. An example
gotcha case is "what happens when you add some new type of system that
specifies the syslog.conf like concept in a different way?".
References:
|
|
