June 21, 2012
5:01 p.m.
Igor Stasenko wrote
is that primitive failed before? from other side, answering #badPath.. is nicer than answering nil
I'm not sure I understand, but I'm not saying (necessarily) get rid of #badPath.., as there is apparently a good reason for it. I'm saying if the primitive fails - let's say the plugin is missing or whatever - we should distinguish that from #badPath.. -- View this message in context: http://forum.world.st/badDirectoryPath-tp4635913p4635985.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.