is that primitive failed before? from other side, answering #badPath.. is nicer than answering nil (like opening a stream on non-existent file) so, you can be sure that problem is not in something not properly initialized. On 21 June 2012 18:18, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2012-06-21, at 18:09, Sean P. DeNigris wrote:
Camillo Bruni-3 wrote
I would assume mostly due to performance....
We should be clear on the reason and put a comment. This is an unusual (cough... c-like) pattern in Smalltalk.
Also, lookupDirectory:filename: returns #badDirectoryPath on primitive failure. Is that a good idea? It seems like it could lead to confusing errors ("what do you mean bad path?!?! I'm looking right at the @%#$ file!). Why not send primitiveFailed?
indeed!!
-- Best regards, Igor Stasenko.