On 17 September 2013 02:12, Jiří Zárevúcky <[email protected]> wrote:
> On 17 September 2013 00:08, Jakub Jermar <[email protected]> wrote: > >> - async_exchange_begin(), does not require you to test for NULL return >> value; as I was told at the camp, the exchange-consuming functions >> should handle this gracefully; for example in vfs_connect_internal() >> > > Ok, so this is actually not always true. > I haven't checked all the functions, but async_send_*() followed by > async_wait_for() would fail an assertion here. > > Ah, sorry, that does not count, since I should check the result of async_send_*(). In any case, I should be able to differentiate failure to allocate resources and failure of operation. async functions return ENOENT in case of NULL exchange, which in case of VFS is very inappropriate. Sorry about late night spam. -- Jirka Z.
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
