Cygdaemon - planning

Elfyn McBratney elfyn@cygwin.com
Thu Jul 3 16:35:00 GMT 2003


On Thu, 3 Jul 2003, Larry Hall (RFK Partners, Inc.) wrote:

> Elfyn McBratney wrote:
>
> > On Thu, 3 Jul 2003, Christopher Faylor wrote:
> >
> >
> >>On Thu, Jul 03, 2003 at 11:57:28AM -0400, Earnie Boyd wrote:
> >>
> >>>Christopher Faylor wrote:
> >>>
> >>>>I think Earnie is saying that well-written code would notice the ENOSYS
> >>>>error and use alternative solutions at run time.
> >>>
> >>>Correct, and the cygwin-apps review process would need to consider it
> >>>manditory for the package acceptance/upgrade process.
> >>
> >>But Corinna wasn't necessarily concerned about official cygwin packages,
> >>if I am understanding this correctly.
> >>
> >>(Can you tell that I don't have a really strong opinion on this one way
> >>or the other?  :-))
> >
> >
> > Me neither. :-)
> >
> > If the caller doesn't check the return value, then it's not our fault, and thus
> > not out problem. :-)
>
> In relative terms of course.  Whether "our" fault or not, the list will
> be the first place the confused user turns.  It behooves us to find a way
> to mitigate, if not eliminate, this list noise if at all possible.

It's just good programming practice IMO, which, granted, a lot of Cygwin list
user's do not have. ;-) If we start getting lot's of confused gnomes trying to
use, say shmop, and have problems..it could become a new FAQ. :-) I'm lloking
forward to. It certainly makes a change from "wtf is su?!?!?" type questions.
Cygserver's motto could be "We're mean..even when remote!"..

Elfyn
-- 



More information about the Cygwin-developers mailing list