in reply to Ram file bug?


I guess that it is a bug since the behaviour is different than when opening a physical file.

Out of curiosity, is there any particular reason that you need to open an in-memory filehandle in ':raw' mode? I would have imagined that it would have been the behaviour anyway, even on Windows.

--
John.

Replies are listed 'Best First'.
Re^2: Ram file bug?
by BrowserUk (Patriarch) on Feb 16, 2006 at 10:37 UTC
    I would have imagined that it would have been the behaviour anyway, even on Windows

    Actually, that was exactly what I was trying to verify when I encountered the bug. Any normal file opened without specifying ':raw' gets ':crlf' by default. I just wanted to confirm that if I wrote to a ram file, then wrote the result to disk that I wouldn't get the crlf translation twice.

    Instead, I got nothing at all :)


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
      You proabably know that you can use open to change the defaults
        You proabably know that you can use open to change the defaults

        Actually, I didn't. Thanks for bringing it up, I don't recall having seen it mentioned here before.

        That said, it doesn't appear to affect this particular case as it seems it only applies to the 2-arg varient on open and/or the STD* handles.


        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.