Re: [Pharo-users] Problems to serialise object when using FileSystem memory

2015-09-02 Thread Stephan Eggermont
On 02-09-15 19:17, Juraj Kubelka wrote: Hi, I think the main problem is in the StandardFileStream class>>#forceNewFileNamed:do: that converts aFileReference into a string and then it tests if the file exists. If this method is correct, then FLSerializer>>serialise:toFileNamed: should not use

Re: [Pharo-users] Problems to serialise object when using FileSystem memory

2015-09-02 Thread Juraj Kubelka
Hi, I think the main problem is in the StandardFileStream class>>#forceNewFileNamed:do: that converts aFileReference into a string and then it tests if the file exists. If this method is correct, then FLSerializer>>serialise:toFileNamed: should not use it. I have an impression that MemorySto

Re: [Pharo-users] Problems to serialise object when using FileSystem memory

2015-09-02 Thread Stephan Eggermont
There is some code missing in the memory filesystem. MemoryFileSystemEntry has binaryReadStream and readStream, but only writeStreamDo: That means that MemoryStore openFileStream:writable doesn't work. Stephan

Re: [Pharo-users] Problems to serialise object when using FileSystem memory

2015-09-01 Thread Mariano Martinez Peck
I am quickly answering without testing (I can do that tomorrow otherwise). Did you see #serializeToByteArray: ? and FLInMemoryBasicSerializationTest? This is not filesytem, but still an in-memory stream. Also, did you make sure the in memory stream of FileStream is binary and not text? Try sending

[Pharo-users] Problems to serialise object when using FileSystem memory

2015-09-01 Thread Juraj Kubelka
Hi, I am writing test case that uses following strategy: -=-=- | memory file | memory := FileSystem memory. file := memory workingDirectory / 'file.fuel'. FLSerializer serialize: {1. 2. 3} toFileNamed: file. -=-=- But it does not work because in StandardFileStream class>> #forceNewFileNamed: a