June 21, 2012
4:08 p.m.
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? -- View this message in context: http://forum.world.st/badDirectoryPath-tp4635913p4635948.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.