Hi guys,
I'm looking at this issue: http://code.google.com/p/pharo/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty&groupby=&sort=&id=5870#makechanges.
And debugging, it seems that the primitive
rename: oldFileFullName to: newFileFullName
��� "Rename the file of the given name to the new name. Fail if there is no file of the old name
��� or if there is an existing file with the new name."
��� <primitive: 'primitiveFileRename' module: 'FilePlugin'>
��� ^nil
is not failing as it says it should in the comment.
Has this behavior changed lately?� Should this be fixed in the vm side, wait for NativeBoost? Or we should just by now fix the comment and clients not to expect that?
some pointer?
Tx