June 21, 2012
4:18 p.m.
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!!