Originally at 2015-06-13T19:09:56Z by Herbert Vojčík
The stream operations nextPut: and nextPutAll: are in fact low-level operations. The high level operation to put an object into a stream (which then translates to to low-level ones) is either write: or << (they both do the same).
Code in Amber core that uses nextPut: / nextPutAll: as regular way to put data on to a stream should be changed to use the high level operations instead.
Originally at 2015-06-13T19:09:56Z by Herbert Vojčík
The stream operations `nextPut:` and `nextPutAll:` are in fact low-level operations. The high level operation to put an object into a stream (which then translates to to low-level ones) is either `write:` or `<<` (they both do the same).
Code in Amber core that uses `nextPut:` / `nextPutAll:` as regular way to put data on to a stream should be changed to use the high level operations instead.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/21879646-fix-code-using-nextput-all-to-use-or-write?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github).
</bountysource-plugin>
Originally at 2015-06-13T19:09:56Z by Herbert Vojčík
The stream operations
nextPut:
andnextPutAll:
are in fact low-level operations. The high level operation to put an object into a stream (which then translates to to low-level ones) is eitherwrite:
or<<
(they both do the same).Code in Amber core that uses
nextPut:
/nextPutAll:
as regular way to put data on to a stream should be changed to use the high level operations instead.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Done in export/import.