30 Mar
2010
30 Mar
'10
5:15 p.m.
On Tue, 30 Mar 2010 21:02:23 +0400, Samium Gromoff _deepfire@feelingofgreen.ru wrote:
On Tue, 30 Mar 2010 09:00:55 -0500, Robert Goldman rpgoldman@sift.info wrote:
Is there some reason why the other choice mentioned --- catching an error from load and then re-signaling it with the additional information about the system --- cannot be used?
Sorry that I didn't make it clear, no there's no reason at all.
Actually nevermind, I was entirely confused and thereby needlessly confusing in the previous mail -- I, for some reason assumed that changing the status quo implies we'd have to get rid of the precise condition.
Yes, there's entirely no reason for not catching FILE-ERROR /within/ ASDF, instead of proactively preventing it (in a racy manner).
--
regards,
Samium Gromoff
--
"Actually I made up the term 'object-oriented', and I can tell you I
did not have C++ in mind." - Alan Kay (OOPSLA 1997 Keynote)