Re: Reducing application footprint: large text files

One thing that I would definitely do is to put all of this logic into one – possibly two – Perl modules which are tasked with maintaining the entire storage system. I would also "future-proof" the design by prefixing the file with a file-version identifier so that the file, whatever it turns out to be, is "self-describing" to programming that is in the know ... programming which occurs in exactly one place or set of places.

Comment on Re: Reducing application footprint: large text files

Replies are listed 'Best First'.
Re^2: Reducing application footprint: large text files by BrowserUk (Patriarch) on Feb 28, 2018 at 23:19 UTC
@theOP: One thing you definitely want to do, is ignore the guy (sundialsvc4 ï¿½incognitoï¿½â„¢) I'm responding to. See http://perlmonks.com/?node=worst+nodes and scroll to the bottom to see why. 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". The enemy of (IT) success is complexity. In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit	[reply]
Re^3: Reducing application footprint: large text files by Anonymous Monk on Mar 01, 2018 at 01:08 UTC
I went to that link, scrolled down to the bottom (and middle, and toward the bottom :)), but the reference eludes me, sorry. Matt.	[reply]
Re^2: Reducing application footprint: large text files by Anonymous Monk on Mar 01, 2018 at 01:04 UTC
The designers of this (not me) are on the same page. This data file is a separate module with a versioned module name. Good to know this, at least, meets the best practice. Thanks, Matt.	[reply]