Or, as the saying goes: Be gentle to any input and strict with output. One of the most important aspects of data handling libraries is resilience against 'unusual' input. Personally I would not only start to think about dropping either format. Talking about design decisions of your new software is rather off-topic here, so readers may ignore the following. It's not uncommon to parse text created on some odd late 1970s system, as it my contain important business numbers. Keep in mind, Data can come from many systems (not just ac or PC) and is of varying age. Chances for this to happen is all within the use szenarios of your library. My question is what impact would such obsoletion have?Īs you already assume, it may break compatibility in some Situations. Data is not just produced by Macs, but many other systems as well. Just make sure it's never used with old(er) data.
If it's guaranteed that all data will be produced by Mac Software less than ~5 years old, chances may be good. If you're sure that all input will be LF delimited, then narrowing it down might work fine. Is the CR line ending still prevelant on new applications or should it be considered legacy?Īs usual it all depends on the environment your software is used in.
