Le 28/10/16 �� 10:33, Marcus Denker a ��crit��:

This seems this error:

https://pharo.fogbugz.com/f/cases/19227/Writing-a-File-with-a-relative-path-to-the-working-directory-results-in-FileException-cannot-open-file

and this is caused by it, too.

https://pharo.fogbugz.com/f/cases/19064/Fuel-out-stack-not-working

I wonder why we do not use FileSystem for all these file related operations?

we should!

On 28 Oct 2016, at 04:34, Arturo Zambrano <arturo.zambrano@gmail.com> wrote:

Hi All,

I'm porting (no big changes) code from pharo 4 to pharo5.

In (*) the resulting file handle is nil. Not sure why, may it be something related to the recent Mac OS X upgrade ��to Sierra?

The same code was working with Pharo 4 on El Capitan.

The calling code is a Fuel serialization.

openForWrite: writeMode��

"Open the file with the given name. If writeMode is true, allow writing, otherwise open the file in read-only mode."

| fileHandle |

(*) fileHandle := self basicOpenForWrite: writeMode.

fileHandle ifNil: [ FileException signal: 'cannot open file: ', name ].

^ (BinaryFileStream handle: fileHandle file: self forWrite: writeMode)

register;

yourself

any advice is welcome.

arturo