Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wish: add back READ/binary and WRITE/binary #2382

Open
Oldes opened this issue Jun 17, 2019 · 2 comments
Open

Wish: add back READ/binary and WRITE/binary #2382

Oldes opened this issue Jun 17, 2019 · 2 comments

Comments

@Oldes
Copy link

Oldes commented Jun 17, 2019

If there is something what I must change in almost every old Rebol2 script to have it working with Rebol3 and or Red, than it is this change of read and write refinements.

Red does not have /string refinement and instead has /as encoding, which may be also fine to support. I know, that this R3 change was done to have read/write as low level, but I believe that we don't have to be so low and to be limited only with binary.

I think that it is ok to keep the default binary behaviour, but it would be also nice to have a chance to refine the required actions. Especially when read/write may be used for more scheme types than files or http request.

Related wish: #2007

@Oldes Oldes changed the title Wish: add beck READ/binary and WRITE/binary Wish: add back READ/binary and WRITE/binary Jun 17, 2019
@rgchris
Copy link

rgchris commented Jun 17, 2019

Related blog posts: Pruning down READ and WRITE, More about Port layers - the OSI Model (the compromise being Finalizing READ and WRITE with many strong opinions in comments)

@hostilefork
Copy link
Member

This still seems to me to be a big open area.

I think if I had to pick a side, I would say keep READ and WRITE as byte-oriented, then let LOAD and SAVE bring in higher level decodings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants