Re: API conflicts

["Bradd W. Szonye" <bradd+srfi@xxxxxxxxxx>]

> Bradd W. Szonye wrote:
>> That's why it "raises an exception" rather than "signals an error."
>> While it isn't necessarily an error, it is an exceptional condition,
>> because the procedure can't supply the requested data.

scgmille@xxxxxxxxxxxxxxxxxx wrote:
> Nevertheless, I'm not sure its a good fit with whats happening.  
> Besides, both models are possible with an absence thunk:
> 
> (define (absence-exception) (raise foo))
> 
> (operator value absence-exception)
> 
> ... while the absence thunk itself is conceptually and mechanically 
> simpler.

I wouldn't go that far, but I'll agree that the exception-raising method
is not clearly superior. Therefore, this is a matter of personal
preference, barely even a minor issue.
-- 
Bradd W. Szonye
http://www.szonye.com/bradd