in reply to Re^3: Deciding for a file access method - requesting opinions
in thread Deciding for a file access method - requesting opinions

I seem to be unable to convey my intention. I already did what you suggested. My library can be used to convert the binary data into a JSON representation (parse) and also to convert a JSON-representation into binary (serialize). These are 2 separate process steps that do not need to be executed back-to-back.

I'm not trying to figure out how to prevent concurrent access. I'm just not sure whether it's better to access the binary data as a simple file handle, as a scalar or as a memory-backed file handle.

But I may already have my answer: Since I'm not developing for embedded devices I'm not memory-constrained and should just load the full file into memory. (Option 'b' or 'c') Since I'm already using read, seek, tell, print to access the bits and bytes I should then go for Option 'c'.

  • Comment on Re^4: Deciding for a file access method - requesting opinions

Replies are listed 'Best First'.
Re^5: Deciding for a file access method - requesting opinions
by BrowserUk (Patriarch) on Jul 15, 2015 at 14:30 UTC
    I'm not trying to figure out how to prevent concurrent access. I'm just not sure whethe

    Then re-read your pros & cons for the 3 methods you describe and eliminate all mentions of "must protect file from change" and similar.

    How do you expect us to understand your motivations when you describe your priorities this way?

    For the rest; for files up to 1/4 GB it doesn't matter whether you slurp them, so use whichever method fits with whatever you have used in your "working parser".

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
    I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!
[reply]

      @concurrency mentions: I see. I have updated the node accordingly.

[reply]

In Section Seekers of Perl Wisdom