In Cygwin, OCaml outputs CRLF line endings but inputs only LFs leading to...
This is interesting and reminds me of a suggestion I made recently, i.e. if we define a let-operator: let ( let& ) ch fn = Fun.protect ~finally:(fun () -> close_in ch) begin fun () -> fn ch...
View ArticleIn Cygwin, OCaml outputs CRLF line endings but inputs only LFs leading to...
We should probably discuss this elsewhere, but I recommend changing the code in pfff so that the same function or block of code both opens and closes the file. I don’t see an advantage of leaving a...
View ArticleClik here to view.
In Cygwin, OCaml outputs CRLF line endings but inputs only LFs leading to...
fasiha: My confusion starts though with this idiom for reading such a file (which I saw in the Semgrep source): let chan = open_in file ;; let len = in_channel_length chan;; let res =...
View ArticleClik here to view.
In Cygwin, OCaml outputs CRLF line endings but inputs only LFs leading to...
fasiha: I entirely place myself at the mercy of your greater experience—it feels like a bug that in Cygwin, when I use this natural-seeming idiom of open_out , output_string , open_in , and...
View ArticleIn Cygwin, OCaml outputs CRLF line endings but inputs only LFs leading to...
I know there’s a glaring flaw in my mental model for how OCaml on Cygwin (i.e., on Windows but with Cygwin-provided OCaml) handles newlines and I’m hoping someone can elucidate the right way to think...
View Article
