From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri,  9 Jun 2006 18:04:53 -0700
From: Roman Shaposhnick <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] quantity vs. quality
Message-ID: <20060610010453.GF2291@submarine>
References: <20060610015739.GA21966@ionkov.net>
	<59f06232334eddd74b8f1c78efe5621b@quanstro.net>
	<20060610001024.GB2291@submarine>
	<20060610023116.GB22180@ionkov.net>
	<20060610004529.GD2291@submarine>
	<20060610030123.GA22488@ionkov.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <20060610030123.GA22488@ionkov.net>
User-Agent: Mutt/1.4.2.1i
Topicbox-Message-UUID: 6704fd08-ead1-11e9-9d60-3106f5b1d025

On Fri, Jun 09, 2006 at 09:01:23PM -0600, Latchesar Ionkov wrote:
> On Fri, Jun 09, 2006 at 05:45:29PM -0700, Roman Shaposhnick said:
> >   Now, don't get me wrong -- sometimes you have to make an extra effort
> >   to at least pretend that it is solvable. Especially when you are in a
> >   business of building commercial software. I can appreciate it. But lets
> >   move our discussion to a practical level -- could you explain what 
> >   sort of "alternative" control flow you're after when something bad
> >   happens inside the library. What kind of an ideal world solution
> >   would you like to see as an application developer ?
> 
> Umm, like returning an error? :)

  If its about 
    $ echo "I can't remember the syntax" > /dev/complicated/device

  sure thing -- I'm with you and I'd be the first one to argue for 
  fixing places where it reboots your system instead.

  What I'm after, however, is a: we are deep in a library, and 
  a really bad thing(tm) happens, how do we recover if we can't guarantee
  that we would be able to even get to the application layer from
  where we are. I'm seriously curious -- do you know of a good strategy ?

Thanks,
Roman.