ENLINE does not convert line endings to native OS format

[Siskin-Bot]

Submitted by: abolka

Contrary to the docstring, ENLINE seemingly only ever converts/normalises line endings to CRLF.

On Linux (native line ending: LF), I'd expect the following to hold:

"foo^/bar" = enline "foo^/bar"

---

^{Imported from: CureCode [ Version: r3 master Type: Bug Platform: All Category: Native Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#2191}

Comments:

Rebolbot commented on Jan 26, 2015:

Submitted by: abolka

In the core-tests suite.

---

Rebolbot added Type.bug and Test.written on Jan 12, 2016

---

Hostilefork added Type.bug, Test.written, Ren.important on Mar 26, 2018

---

Hostilefork commented on Mar 26, 2018:

Regardless of what the docstring says, having the same code process the same data on different platforms differently is a variation in behavior that is a fairly questionable idea.

There may not be as much benefit to embracing such variations as there is to pushing people away from the need for CR LF in general. See comment here:

metaeducation#1517 (comment)

These are the tests which were added, which show the behavior that I don't think is necessarily a great idea:

[    
    equal?
        "^/"
        deline choose [
            system/version/4 = 3  "^M^/" ; CR LF on Windows
            true                  "^/"   ; LF elsewhere
        ]
]

[
    equal?
        enline "^/"
        choose [
            system/version/4 = 3  "^M^/" ; CR LF on Windows
            true                  "^/"   ; LF elsewhere
        ]
]

---

Hostilefork mentioned this issue on Mar 26, 2018:
ENLINE doesn't handle block! arguments.

---