Re: Why does operate return no value?

Gary King wrote:
> Can anyone recall the design decision behind operate returning no  
> values?
> 
> It would be nice (especially for things like 'test-op) to get a value  
> back so that one could, for example, do
> 
> (unless (asdf:oos 'asdf:test-op 'my-system)
> 	(error "My system failed its tests, bummer."))
> 
> thanks,
> --

I agree.  Failing that, I wish there were some specification of what
some of these operations should do.  For example, if test-op does NOT
return a value, presumably it should write something to <some specified
stream>, or raise <some specified condition> when the tests fail.  If
there are multiple tests in a test-op, perhaps it should print something
when each such test is run.

Without such a specification, it is hard for someone to build a
reasonable test-op (are my RT-based tests appropriate?) for a system,
and hard for someone to know how to consume them (e.g., if the test-op
simply prints things to a specific stream --- not the choice I would
prefer --- I might want my code that uses the test-op to redirect that
stream and then grovel over its contents).

Best,
R


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV